Member-only story
Using .NET MVC as front-end and Web API as back-end
A simple approach to develop modular web apps without leaving Visual Studio.
I have been developing web applications for 5+ years and have worked on multiple technologies to build front-end including ASP.NET WebForms, MVC, Angular & jQuery (not to forget HTML, CSS & JavaScript).
When I first got introduced to Angular, I liked it very much as it enabled true separation of UI and business logic. I built the front-end in Visual Studio Code using Angular and back-end using Web API in Visual Studio. The only pain-point was to work with two separate IDEs. I know that in an ideal scenario these two are jobs for separate people, but for smaller projects (and limited people in my workforce), I prefer to get this done single-handed. I tried to explore possibility of using Angular inside Visual Studio but that required too much config and still did not seem to have full support (this may have changed now).
Recently I got my hands on another small project and I started exploring my options to do all development inside one IDE. Since my preferred technology for back-end was still Web API (with EF & SQL), I had to find a solution that worked inside Visual Studio.
ASP.NET MVC offered a good choice for building extension-less URLs and handles routing very well at server side, I decided to build a…
