MIX 2008 and the Road-map of the ASP.net MVC framework

ScottGu recently posted some messages on the mix 2008 and ASP.net MVC framework.

Say 2007 of the video I have not seen how much, 2008 will come out again. There's always something to be pushed by Microsoft at every year's mix, like the 06 asp.net AJAX (or atlas, if it's not mistaken), the 07 Silverlight, so what's in the mix Congress of 08? Scott has given us some options in this article:

IE 8

IIS 7.0

asp.net (including asp.net 3.5, asp.net AJAX, asp.net MVC, and asp.net Dynamic Data)

VS 2008 and Expression Studio

Wpf

Silverlight 2

And much more ....

In the light of past experience, I estimate that the focus should be on the content of the ASP.net series. Microsoft's ASP. NET team is currently in the hands of a lot of tasks, there are many large and small framework/components need to develop and improve--but as long as one thing is successful and widely used in the industry, then their purpose is achieved. Microsoft so many cattle people are not eating ganfan after all.

The most popular community (or Microsoft) in the ASP.net series should be the ASP.net MVC framework, the only new gadget in the ASP.net series that can be called a framework--asp.net Ajax is no longer new. Scott also recently released the latest news about the ASP.net MVC framework, and the main thing is that aps.net MVC will release a "asp.net MVC framework MIX Edition" for a few weeks MIX08-hehe, This name is my random, in fact, should be called "asp.net MVC MIX Preview release", from the content of the article to see the changes are not small, and seems to be of considerable value:

The ASP.net MVC framework can run at the partial trust level: Remember ASP.net Ajax encounters with a virtual host? asp.net ajax can only be installed on the server by the virtual host server because it must be run under the full trust level asp.net ajax. The ASP.net MVC framework can run at the partial trust level, which means that we only need to copy the relevant DLLs to the bin directory.

There is an enormous increase in infrastructure such as URL routing: Only URLs that are better able to support restful are mentioned in the article. I sometimes think, asp.net mvc URL routing actually embodies is "the agreement is better than the configuration", if to "strong" function, is it necessary to a considerable degree of configuration? We can only wait and see if we don't talk about more details.

Enhanced VS 2008 Support: Visual Studio is actually a platform, highly scalable, and Microsoft's ability to attract more developers to make its own things more competitive naturally requires the support of powerful tools. The template for creating a project is also supported, and from the content of the article, at least one of the templates for test project appears, but it seems that the UI is rudimentary-well, after all, it's just a Preview.

Removed controlleraction custom attribute: In the previous CTP, Controller's action needs to be marked with Controlleractionattribute, which is not needed in the future. The change is said to be due to community feedback, but I don't mind that.

Filter Attribute: New function. Custom attributes are. NET is a very powerful feature, the code implementation can be very beautiful. For example, according to the article, ASP.net MVC will enable controller and action to support the extensible filter mechanism, and the framework itself will implement some of the most common features, such as caching and authentication mentioned in the article, which I have to say is really strong.

Built-in HTML Helpers: In fact, the original in the MVC Toolkit Library integration into the direct framework of the class. Of course, new helper classes and methods will certainly be added.

A great deal of refactoring and design improvements: This will certainly make the ASP.net MVC framework a good learning material-and a lot of technical writer writing material. Just searched the book about ASP.net 3.5, found that there are a lot of, but still missing several important series, such as Wrox Professional series and O ' Reilly essential xxx and programming xxx. After each technology emerges there will always be no less, but so many books keep me out of the question, so I now generally look at MSDN and community articles.

The ASP.net MVC framework will advertise the source code for debugging, compiling, and patching: I'm actually more concerned with the implementation of ASP.net MVC, such as how it works under the partial trust level. After the release of the source code directly solve the problem of looking at the code, of course, debugging is also a cinch. As for tinkering, according to Scott, Microsoft will certainly not allow third parties to asp.net MVC changes, so the real patch will only be done by Microsoft. The purpose of the release of the source code is to facilitate users to find the problem can be repaired on their own, or what needs to expand their own-"quietly into the village, shooting the Don't".

Let's sum it up first.

But I'm wondering why I didn't mention it. NET parallel Library, is it still "take not to sell"? Actually, I really like that thing ...