ASP.NET MVC in a corporation – part #1

Posted by – August 25, 2009

.NET LogoEach big organization like this in which I work is mostly based on processes. Everything from purchase orders to computer hardware is described by them. To be honest I am not a big fan of this way of work. My mind is closer to Agile way of thinking rather than stiff procedures for solving problems but from a bigger perspective this approach seems to work because my current employer has over 100 years and is in very good health.

One thing which is quite funny with processes is that someone has to figure out how each of them should work. In case of my department, which is very young and in its nature very different than rest of the organization, there is no process for many things and we have to develop them for our own. One of our processes is “software development process”. Because the department consists of about 300 developers, administrators and IT specialists and we are using wide range of tools and technologies, the process I mentioned above is very general and describes things in a high level. In order to be able to use it and be safe in case of internal or external audit we need many supporting documents which customize it to a needs of particular team. This detailed documents describe how we should do development in a particular technology (for example .NET Framework), what tools, libraries, methodologies can we use etc. Of course we do not choose tools with which we will work only basing on our subjective opinions and feelings. During choosing process each technology or tool is evaluated by a group of specialist (developers, administrators) and compared to its competitors/equivalents which are available on the market.

Currently I have a pleasure to initialize a process of ASP.NET MVC evaluation. Its purpose is to check if this framework can be used as the replacement for ASP.NET Web Forms and Model-View-Presenter pattern which we are using now. Because the evaluation process does not touch only ASP.NET MVC but also other presentation framework for web .NET application me and my teammates had to prepare a list of things to check and evaluate:

  • Data binding
  • Validation
  • Navigation
  • State saving
  • Embedded controls support
  • Testability
  • Security
  • Collaboration between developers and UI designers
  • Adoption to existing projects
  • Extensibility
  • Community support
  • Documentation availability
  • Development tools support

Order in which topics on the list appear is accidental and all items are in my meaning equal in theirs importance.

Because I am currently at the beginning of the ASP.NET MVC evaluation I do not have to much more I could share with you. Only thing I have prepared is a mind map with detailed topics I will have to take a look at. I will provide more information about pros and cons of the framework for a big companies in a next posts. If you would like to hear about something regarding this topic please leave your comment below.

Hey, keep in touch!! Follow me on Twitter, @marcinobel or subscribe to this blog.
3 Comments on ASP.NET MVC in a corporation – part #1

Respond | Trackback

  1. [...] link is being shared on Twitter right now. @bik, an influential author, said Marcin Obel » Blog Archive [...]

  2. [...] to VoteASP.NET MVC in a corporation – part #1 (8/24/2009)Monday, August 24, 2009 from Marcin ObelEach big organization like this in which I work is mostly [...]

  3. [...] my previous post I have mentioned that I am currently evaluating the ASP.NET MVC in context of usage for building [...]