Development

Welcome back! In this series, we are exploring how to design HTML forms with AngularJS, with the best user experience in mind. If you missed part 1, you can find that here. In part 2, we will take a deeper look at a couple more complicated validation scenarios.

One of the greatest benefits we have seen when creating single page applications with AngularJS is how much faster and easier it is to design forms, even those with complex validation.

The single page application (SPA) approach has revolutionized our approach to development.  Fantastic client-side Javascript frameworks like AngularJS, Knockout, and React have made the transition easy and fun.  As we’ve written more and more SPAs an unexpected trend has emerged.  We’ve moved to a thin server architecture for delivering our back-end solutions on SPA projects.  We increasingly think of the application tier as plumbing, only responsible for data storage with a little authentication, authorization, and validation thrown in.

One of our clients provides an information-rich website for their customers, containing business data from multiple sources.  Like all companies, our client wants to make their content easily accessible for their website users; however, without a unified search for business data strategy our client could only provide search for a small portion of their data.

In our last article we described the Service and Presentation layer choices in our ASP.Net MVC application template.  In our fourth and final article on ASP.Net MVC Principles, we discuss BHW's Visual Studio project template and how it helps us quickly start projects with a great foundation.  We also discuss when to apply the template and some of the value the template brings to our projects.

In parts one and two of our four part series on ASP.Net MVC Principles we discussed the object oriented design concepts behind our application template.  We also discussed Dependency Injection and how our application template is divided into three layers, Data Access Layer, Services Layer, and Presentation Layer. We described the Data Access Layer in the last article.  In this article we will describe our services and presentation layers.

In our first article we explained the object oriented design patterns behind our ASP.NET MVC Principles.  Here we explain how our MVC projects are divided into different abstraction layers and how those layers interact via Dependency Injection.

Our clients often ask us to explain the architecture decisions behind the ASP.Net MVC principles in our standard application template. We’ve had these discussions a number of times and felt it would make a great blog series. Here we start with our first part of a planned four-part series describing our MVC project template.