welcome to XRM blog

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. 

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!

Expanding a portal to cover multiple regions and/or languages can be quite a handful of a job. This can be done in two ways, either making the portal multilingual or making separate portals for each region or language. Language localization is the process of translating a pre-existing portal into any given language.

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

Our client off late reported unusual user registration on their DNN websites. They experienced a peek in user registration. They asked for us to investigate the issue and eagerly obliged. It turned out that all registrations were taking place with unique emails and had address etc too. Soon it turned out to us that these are bots that are creating these users and then utilizing activity feed to share spam links. 

With the advent of MVC it is imperative for all programmers to understand the different ways this framework provides to share data from Controller to View. Each solution has its pros and cons. But my advice to you is stick to the method which is most comfortable to you and accepted by your team lead.

Some of the biggest advantages of ASP.NET MVC are that it is built on a solid tried and tested MVC architecture and the removal of view state concept. Added to that is the beautiful concept of separation of concern through Views and Controllers. Microsoft keeps on adding to this frame work and in a very short period of time it has reached its version 5. We look into some new features introduced in version 5 and version 5.1. This information has been gathered from Microsoft site and msdn.

ASP.NET is a development framework that provides facility to build web pages and sites incorporating CSS, java script, Html and server scripting.

Development becomes very easy using these three types of Asp.net.

1. Web Pages

2. MVC

3. Web Forms