Asp Dot Net – MVC

I’ve gone through 4 different online training courses now for Asp.Net MVC projects, and each one does the same thing differently.

That’s not surprising, because there have been so many flavors of Asp.Net MVC over a very short period of time. I’m finding it helpful to actually go through all of the different presentations, because it helps to see how things have progressed, and to be able to see examples online that may relate to your project, but use a different implementation method.

One of the things I found the most confusing was different implementations for presentation, data binding, and event handling. In the classic MVC using C# Models, Views and Controllers, much of the layout is performed using Dot Net controls calling more directly into the web site. The newer versions seem to take advantage of frameworks such as Bootstrap for layout, rather than using classic HTML tags, or the Dot Net controls. In this scenario, a lot more work tends to be done on the client side, and a lot more code is included in ViewModels implemented in JavaScript pushed to the client.

One thing I found common, regardless of implementation, was that validation needed to be performed on both the client and server side of things. As to the rest, I’m still working through the benefits of each implementation.

At this point, the key things I have been able to identify which may determine your implementation are things such as bandwidth, number of anticipated users, amount of data needed to handle tasks, client responsiveness, adapting to different display form factors, security, exposure to the web, re-usability, and ease of implementation.

One thing is for sure, I have not seen any two different projects implemented the same way. My take away from this observation is that I can learn strategies from each of these different patterns and apply them as they fit best.



Tags: ,