var subtextAllowedHtmlTags = ['a', 'b', 'p', 'strong', 'blockquote', 'i', 'em', 'u', 'strike', 'super', 'sub', 'code']; var subtextBlogInfo = new blogInfo('/', '/'); Archives Contact Resume ... Print Haacked.Library.googleAd(468, 60, "468x60_as", "text", "3629720158", "FFFFFF", "FFFFFF", "FB4727", "000000", "FB4727"); At this yearâs Mix conference , we announced the availability of the second preview for ASP.NET MVC which you can download from here . Videos highlighting MVC are also available Now that I am back from Mix and have time to breathe, I thought Iâd share a few (non-exhaustive) highlights of this release as well as my thoughts on the future. New Assemblies and Routing Much of the effort and focus of this release was put into routing. If youâve installed the release, youâll notice that MVC has been factored into three assemblies: - System.Web.Mvc System.Web.Routing System.Web.Abstractions
The key takeaway here is that MVC depends on Routing which depends on Abstractions Routing is being used by another team here at Microsoft so we worked on making it an independent feature to MVC. MVC relies heavily on routing, but routing doesnât have any knowledge of MVC. Iâll write a follow up post that talks about the implications of that and how you might use Routing in a non-MVC context. Because of the other dependencies on Routing, we spent a lot of time trying to make sure we got the API and code correct and making sure the quality level of routing meets an extremely high bar. Unfortunately, this investment in routing did mean that we didnât implement everything we wanted to implement for MVC core, but hey, itâs a preview right? ;) | |
|
