ASP.NET MVC: A New Framework for Building Web Applications
- Posted: Oct 29, 2008 at 9:35 AM
- 29,228 Views
- 13 Comments
Download
How do I download the videos?
- To download, right click the file type you would like and pick “Save target as…” or “Save link as…”
Why should I download videos from Channel9?
- It's an easy way to save the videos you like locally.
- You can save the videos in order to watch them offline.
- If all you want is to hear the audio, you can download the MP3!
Which version should I choose?
- If you want to view the video on your PC, Xbox or Media Center, download the High Quality WMV file (this is the highest quality version we have available).
- If you'd like a lower bitrate version, to reduce the download time or cost, then choose the Medium Quality WMV file.
- If you have a Zune, WP7, iPhone, iPad, or iPod device, choose the low or medium MP4 file.
- If you just want to hear the audio of the video, choose the MP3 file.
Right click “Save as…”
- MP4 (iPod, Zune HD)
- Mid Quality WMV (Lo-band, Mobile)
- High Quality WMV (PC, Xbox, MCE)
Learn how the new ASP.NET MVC framework differs from the current ASP.NET Web Forms framework. Learn to take advantage of ASP.NET MVC to build loosely coupled, highly testable, agile applications. See how ASP.NET MVC provides you with fine-grained control
over HTML and JavaScript.
-
Phil HaackAs a code junkie, Phil Haack loves to craft software. Not only does he enjoy writing software, he enjoys writing about software and software management on his blog, http://haacked.com/. Phil is a Program Manager with the ASP.NET team working on the ASP.NET MVC project. Prior to joining Microsoft, Phil worked as a product manager for a code search engine, a dev manager for an online gaming company, and as a senior architect for a popular Spanish language television network, among other things. In his spare time, Phil contributes to various open source projects and is the founder of the Subtext blog engine project, which he recently learned powers the blogs on MySpace China.
Comments Closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
- Although the talk is not about TDD specifically, I'd love to see more about common scenarios and how to test them.
- More information on the different types of action filters we can implement.
- General solution layout best practices, naming conventions, code organization etc.
Complicated MVC never works well in the real world. It's the reason I moved from Java to .NET a few years ago.
Projects are never done on time, it's hard to maintain, large learning curve for a new developer coming in and no one ever wants to work on the code besides the person who originally wrote it.
I'll probably go to this just to hear the reasons why and laugh.
I’ve been developing multi-layered web applications(web forms & APIs) now for 8 years and in my experience the MVC pattern is hands down the best choice for architecting an extensible, maintainable and highly isolated solution. Prior to the ASP.NET MVC framework, I was using the UIP application block w/NET 2.0(I’m serious) that Eugenio Pace and team had put out a guess about 6 years ago? The clean separation of layers & responsibilities throughout the application architecture just makes perfect sense to me. When MS announced they were introducing the ASP.NET MVC framework I knew something great was on the way…and thus far I have been more than impressed the framework, community involvement/support and the team’s responsiveness to the developers currently working with the MVC.
I’m currently working on implementing a solution for my employer that makes use of the ASP.NET MVC framework to expose a REST based API for consumption by internal and in the future external clients. We are currently also making use of the following MS Enterprise blocks:
1. Validation
2. Logging
3. Exception Handling
4. Caching
5. Data
Thus far everything is fitting together very well under the MVC ‘hood’ with the use of some other design patterns such as Façade & factory (abstract) including the ASP.NET membership model. Once the UI component of the application is built, I’m sure we’ll make use of the JQuery framework as well.
Regarding what I’d like to see at the presentation…
Ditto on the previous suggestions:
1. More information on the different types of action filters we can implement (or that are on the way).
2. General solution layout best practices, naming conventions, code organization etc.
3. TDD examples, how-to's - I realize there's a lot of information available on this. However, sometimes seeing a demo(w/Preview 5) really drives the message home.
Perhaps some of these topics could be addressed or discussed:
1. The use of the MVC framework for a REST application that could serve as both an API as well as a data source for UI application(sound familiar?). I believe Rob Conery had an article touching on this topic.
2. The concept of the use of the standard verb/action methods typically associated with REST…should we stick to using the 7 defined actions? Perhaps reason why we should or should not?
1. Index
2. List
3. Show
4. Edit
5. New
6. Create
7. Update
8. Delete
3. Routing best practices & how to configure routes in a config file of sort?
4. What not to do when developing with the MVC…perhaps lessons learned from the team?
5. A road map of the framework…I realize a lot of people have been hounding you guys about this. But any further insight you could provide on when we could expect a release date would be greatly appreciated!
Looking forward to conference!
Cheers,
Kyle
Very interesting presentation you did at PDC2008. Is there a URL where I can get the source code of your presentation (with the usual disclaimers)?
Thanks
Could you also share your visual studio style/theme please?
My eyes feel really comfortable with those colors and fonts settings
Thanks,
Luca
The one that interest me about this MVC is the SEO.
I was wondering whether it's possible to code in web form style, created aspx files in many sub folders, and remap the IIS to treat .html as aspx.
What do you think?
Thanks
@Haacked: Hi Phil,
I'm in the process of starting a major project and still debating what platform to use (WebForms versus MVC). Let's assume this site will have 100,000 users.
I was wondering if you could tell me what is the best practice to keep the user known across pages. I don't believe it's the Session, and I don't want to use the Membership database since I already have my DB and don't need another one.
I'm not too clear if the call HttpContext.Current.User.Identity.IsAuthenticated needs a Membership Database underneath or how does it remember the current user? Is that by the means of a cookie?
If so, is it "bad" practice to create my own cookie and put my own data, as long as I encrypt it before saving on the Response.Cookies ??
Salut from one Fil ...to another Phil
Remove this comment
Remove this thread
close