welcome to XRM blog

In today's rapidly evolving business landscape, the need for innovation and agility has never been greater. Low-code development presents a transformative approach to software creation, offering organizations a streamlined path to development excellence. With XRM "App Genesis" software, businesses can expedite solution design, allowing non-technical users to swiftly assemble applications using intuitive drag-and-drop tools. This acceleration in development ensures minimal backlogs and on-time project delivery, essential for meeting customer expectations in a competitive market.

What Is a SOAP API?

A messaging specification for information exchange between systems and applications is called Simple Object Access Protocol (SOAP). A SOAP API is designed in a manner that is more structured and codified than other application programming interfaces (APIs). Compare SOAP to the United States Postal Service. Sending and receiving communications across systems (and within enterprise applications) is made dependable and trustworthy with its help. Although it can be slower than rival architectural forms like REST, it is more traditional, well-established, and trustworthy.

Securing the Backbone of Modern Web Applications

In today's digital era, web applications serve as the backbone of businesses and organizations worldwide. From e-commerce platforms to online banking and social media networks, web applications facilitate seamless user experiences and provide essential services. However, the increasing reliance on web applications also makes them attractive targets for cybercriminals seeking to exploit vulnerabilities for financial gain, data theft, and reputational damage. Securing the backbone of modern web applications has become a critical priority to safeguard sensitive information and maintain user trust. This blog will explore the key aspects of web application security and the measures to ensure robust protection against evolving cyber threats.

Exploring Web Security Beyond Code

In today's digital age, where everything is connected and accessible through the internet, ensuring the security of web applications and websites is of paramount importance. While developers focus on writing secure code and implementing robust security measures, web security goes beyond just the code. It encompasses various aspects, including infrastructure, network security, user awareness, and more. In this blog, we will delve into the world of web security beyond code, highlighting essential factors and strategies to enhance the overall security posture of web applications.

In today’s world if we are using any service on the internet, we are consuming some sort of APIs in many ways. Even the article you are reading is coming as a response to an API request to our servers. Have you ever thought how you are able to see Google Maps on websites other than Google? That is where the APIs comes into picture.

If you are upgrading the DNN from 07.03.02 to Version 09.XX.XX and post upgrade you are getting the following error  Object reference not set to an instance of an object. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.  Exception Details: System.NullReferenceException: Object reference not set to an instance of an object. Source Error:  An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace:  DotNetNuke.Web.Mvc.MvcHttpModule.SuppressXFrameOptionsHeaderIfPresentInConfig() +327 DotNetNuke.Web.Mvc.MvcHttpModule.Init(HttpApplication context) +13 System.Web.Http ...

Recently we were faced with a unique challenge. One of our mobile apps was posting images to our WebAPI as a Multipart/Form-Data but our WebAPI was unable to receive the byte array and returned null each time. The WebAPI in question was written for an older MVC application. For the Mobile App, the problem was the function was not able to use HttpPostedFileBase class. 

One of the most common issues we face is creating a REST API for our client which is hosted on a brand new domain while the client application is being hosted on the clients old domain. Specifically when client demands that we carry both the system parallel for couple of months until he/she has confidence on the upgraded API's. In our own company we found this issue when launching a brand new domain for a new application. Unfortunately the new application hosted on the new domain talks to our old REST API hosted on our company domain. Problem!

In my previous post here I had discussed about convention based routing which is the default way in Web API. Check it out here.Starting with Web API 2 Microsoft introduced attribute based routing. Which is way more simpler. The reason for introducing this new feature was two folds, one it is easier to understand and maintain, second is the kind of REST calls required.

One of the most confusing aspect of MVC and Web API is the subject of routing. MVC routing looks and feels more logical to most developers as compared to the Web API routing. The reason behind this is that Web API depends on the HTTP verb to match the action being called. It follows a set of conventions which automatically fires a particular action based on the endpoint being hit. This throws of most of us because we are in the habit of calling methods by name.

Hopefully this post will give you a head start at what is the simplest or the default way in which Web API manages its routing based on conventions. I will show all the concepts using simple boiler plate code, don’t focus on the logic inside the Action(method).