I have been developing asp code for quite some time now. I started out with interdev 1.0 way back when. From what I can see we have seen 3 major revisions of ASP.
-
Classic ASP
-
Archiac to say the least but hindsight is always 20-20. Great intro into web development, we started n-tier development here, most sights were done in a 2 tier environment, and at the end of its lifetime we started developing 3 tier environments with SOAP.
-
ASP.Net in all its flavors (1.0,2.0,3.0,3.5)
-
What can we say asp.net is great, and with the integration of web servics and WCF, we can keep great seperation from between our tiers. Ajax was a little cumbersome but eventually you could get it working.
-
ASP.Net MVC
-
After completing my first MVC project, I kind of felt like my brain was a little scrambled. Kind of like the first time I completed my first ASP.Net application. Remember those “Where is my code suppose to go” thoughts only now its. “At what level should I insert this code snippet”. My brain keeps going back and forth on questions about “how things are the same” and “how things are different”. Ultimate question, can we code quicker, more concise, are our objects cleaner. My initial answer would be yes, but it is going to take some getting used to, just as we did for the transition from classic to asp.net.
The purpose of this blog is to discuss MVC, from starting fresh with a brand new MVC project, to how do we integrate MVC logic and technology into our current ASP.Net applications. ASP.Net was nice because we had a clear cut path of bringing in our projects to a VS solution, and converting one page at a time. I don't think it is going to be as easy to convert our applications to MVC. What I intend to do here is help create a road map for readers. More posts will arive shortly. If you have any questions or comments please feel free to shoot me an email at DarrenMcD@yahoo.com. I am always open for good communication after all Iron sharpens Iron.