http://weblogs.asp.net/scottgu/archive/2008/07/14/asp-net-mvc-preview-4-release-part-1.aspx
Another exciting preview will be released very soon. It seems this release will have a few new things for authenticating users as well as Ajax support.
I also learned that PostSharp is not needed for what I was using it for. The framework has something called ActionFilterAttributes that basically do the same thing and more! By providing an ActionExecutingContext value when overriding OnActionExecuting you can now have all sorts of information about the controller and action that have been invoked.
I’ve been diving into some new .Net frameworks and libraries lately and thought I should share some of the cool stuff I’ve learned. I’m going to share what I’ve learned while using PostSharp with the new ASP.Net MVC framework.
I have already posted a few things about the new MVC framework so I won’t explain why Im excited for it. But, I havent talked about PostSharp so lets go over that really quick. First, you NEED to watch this video. It goes over exactly what I am using PostSharp for and shows off its power in just a few minutes. Next, you need to read up on what Aspect Oriented Programming means. The wiki article is pretty complex though. What you need to take away from it is how it helps programmers ’separate concerns’, modularize your code, easily apply ‘aspects/modules’ to various parts of your code and avoid maintenance problems. Another good link is http://www.postsharp.org/aop.net/.
Let’s talk about the sample project now.
Read the rest of this entry »
ScottGu’s Blog -
“The SP1 release of Visual Web Developer 2008 Express adds support for both class library projects as well as web application projects (previously only web site projects could be used with it). This new support is useful in itself, as well as in enabling both ASP.NET MVC and Silverlight project support with VWD Express. If you install the Visual Web Developer Express SP1 Beta you can start using ASP.NET MVC Preview 3 with it immediately.”
Its about time! I hated the fact that you couldnt create Web Application and Class Libraries in the express edition. Now you can do it all! You even get Asp.Net MVC support!
I just learned that the ASP.Net team has released their 3rd preview of the new MVC Framework. Things just keep getting better and better!
http://weblogs.asp.net/scottgu/archive/2008/05/27/asp-net-mvc-preview-3-release.aspx
If you’re the kind of person that likes to just dive into code to learn new things then I highly recommend that you check out the open-source twitter clone called Yonkly. The source was just made available here and was written using the ASP.Net MVC framework. I’m playing with the code right now!
http://www.emadibrahim.com/2008/05/29/yonkly-source-code/
Today I had the opportunity to attend the Utah CodeCamp and I learned quite a few new things. The main reason I wanted to go was to listen to Mark from Medicity give his presentation on the new Asp.net MVC Framework. He probably gave one of the best presentation there today. I made sure it was clear at work that I had high expectations, so maybe that helped?
So what’s the big deal about the new MVC Framework? Oh it’s only the best thing to happen to Asp.net ever! I never really played with classic Asp much but I’m told it has some similarities and you might feel like things are moving backwards, but it really is for the best. If you’re familiar with how JSP (yuck) works with the MVC pattern then a lot of the new things will feel very familiar.
The biggest shock to me was how they have basically eliminated the page life cycle and the traditional postback. Until now, in Asp whenever you wanted to fire some click event the client posted back to the aspx, recreated the entire page again firing off the pageload and all the other junk and THEN invoked the click event. That has always bugged me! It is such waste of time to recreate an instance of a page that you’re probably going to throw away anyway. That’s because the majority of the time you direct the user to different page when they invoke some event. Now, your buttons invoke specific ‘actions’ on your controller and the controller decides what data to pull from the model and what view to use.
I’m not going to go into much more detail now but I’ll try share any new findings in future posts. Until then, check out Scott Gu’s blog for more info!
Thanks Mark for an awesome presentation!
