welcome to XRM blog

This problem is pretty hard to explain until one faces it for the first time. My environment is Azure web app. My code downloads multiple files using a third party REST endpoint on the server side. My ASP.NET UI then downloads it to the client. I don't have the luxury of a server folder aka Server.MapPath

UNIX time or UNIX Epoch is the time format used by JSON, hence developers/consumers of the REST API struggle with the desrialization of such JSON data. In this blog post I give you the simplest option to mitigate this issue. No complicated code just an in-built annotation and all the problems are solved.

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. 

This article presents to you a C# application which will get a list of blob files from an Azure Storage. The key part of this method is the container name and the connection string. Thankfully the container is created by you, therefore, you should know the name and the connection string is available to copy on the Azure Storage portal.

Often when traditional C# programmers start learning javascript based languages or framework, they are confused by the Linux style compiler options and command line statements. All of us want to use our favorite Visual Studio to write code. The same is true for TypeScript too. It can be a steep learning curve for just setting up the development environment. In this blog post, I will try to simplify it in clear steps and show you how you can get Visual Studio and TypeScript singing together inside an ASP.NET project under 10 minutes. 

How often have you faced this situation as an admin when some employee comes up to you and says that a field in a record which he was working on was changed. In most cases these changes have been made by he user which he simply forgot but as an admin you need solid evidence to show him. Sometimes the complain is genuine, the field value was changed by some other person.

Microsoft Dynamics CRM for all its innovation and bells and whistles, seems to have completely forgotten about the humble 'tag'. It isn't something that is a new phenomenon , 'tags' have been around for ages. Anybody who has either done blogging or searched for articles has used the power of tags to categorize articles. Salesforce on the other hand has made the 'tag' our best friend. This little innovation makes working in Salesforce CRM a pleasure, specifically for people who hate to search for records through a maze of menus and submenus. In this particular blog post we will be looking at how to use Salesforce tags to increase your productivity

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).