ASP. net mvc Framework roadmap update

[Original address] ASP. net mvc Framework road-map update
[Original article publication date] Tuesday, February 12,200 8

In February December, as part of ASP. NET 3.5 extensions CTP, we released the first preview version of the new ASP. net mvc framework. I also wrote a few blog posts to provide more details about what the framework is and how you can use it:

• Introduction to ASP. net mvc Framework
• ASP. net mvc tutorial (Part 1)
• ASP. net mvc tutorial (Part 2: URL path selection)
• ASP. net mvc tutorial (Part 3: Uploading viewdata from the Controller to the view)
• ASP. net mvc tutorial (Part 4: Process Form editing and submission scenarios)

Since then, we have received a lot of positive feedback. The download volume is very high and we feel the excitement around this framework. Recently, many people often asked me a question: "When will the new version come out? What are there in it ?"

The following content provides several updates about the new features that the ASP. net mvc development team has been developing and will soon release. In another post in the future, I will discuss ASP. NET Dynamic Data (Dynamic Data) and ASP. NET Ajax features that have been moving steadily.

All these features (ASP. net mvc, ASP. NET Dynamic Data, and new ASP. NET Ajax improvements) will be released later this year, available for vs 2008 and. Net 3.5.

ASP. net mvc mix preview version to be released

We plan to release the next Public Preview of ASP. net mvc at the MIX 08 conference a few weeks later. This version can be downloaded by anyone online (you do not need to participate in the mix ). In this version, we integrate the feedback from many early adopters. The following are some improvements in the next preview:

1) the ASP. net mvc framework can be deployed in the \ bin directory of the application and work under partial trust permissions.

The first ASP. net mvc preview version.ProgramThe set is registered to the GAC (Global Assembly Cache) of the machine, and an installer is required to run on the machine.

Starting from the upcoming preview version, we will allow the application to directly reference the system. Web. MVC. dll Assembly from the application's \ bin directory. This means that you can use ASP without running the installer on the server. net MVC framework, you just need to directly copy your application to remote ASP.. NET Server ).

We are still doing some work to allow the ASP. net mvc Framework to run in "partial and moderate-Trust (partial/medium Trust)" host scenarios. This will allow you to use this framework in a cheap shared host account, instead of requiring the host supplier to do anything (as long as you FTP your application up, it can run, they do not need to install anything ).

2) significantly enhanced path selection features and infrastructure

One of the most powerful features of the ASP. net mvc framework is its path selection engine (I have discussed these features here ).

The forthcoming ASP. net mvc preview will include more URL path selection features and improvements. You can now use a named path (allow explicit reference to path rules) and flexible path wildcard rules (allow custom CMS-based URLs ), introduce and declare custom path rules (scenarios such as rest resource ing are allowed ).

In this preview, we also separate the URL path selection infrastructure from other parts of the MVC framework, which allows us to use it for ASP. other non-MVC features in. Net (including ASP. NET Dynamic Data and ASP.. NET web forms ).

3) Improved vs 2008 tool support

The first ASP. net mvc preview version only supports a very small version of vs 2008 (basically a simple project template ).

The forthcoming ASP. net mvc preview will provide improved vs 2008 integration support. This includes better project file templates and automatic default Project Settings. We also added the built-in "test framework" Wizard, which will automatically run when you create a new ASP. Net MVC project in the file-> new project dialog box. This allows you to easily name your ASP. net mvc application and connect to a unit test project.

The ASP. Net MVC test framework wizard is pluggable and allows custom test project templates to be added to the supported test option tables:

This allows developers to easily select any unit test framework they like most (as well as associated mocking and dependency injection options ).

4) The Controller action method does not require the [controlleraction] Feature

The first ASP. Net MVC preview requires that the action method of the controller class be explicitly marked with the [controlleraction] feature to be called:

Based on feedback from early adopters, the ASP. net MVC will remove this requirement. Instead, by default, all public methods on the controller are regarded as action methods:

Note: You can add features to prevent the public methods of your controller from becoming callable action methods. If you want/need to add a public non-action method.

5) support for new filter features of controllers and action Methods

In the next ASP. net mvc version, a new scalability feature is called "filter attributes. This allows you to interceptCodeThe code can be injected into the request of the MVC controller before and after the Controller or its action method is executed. This behavior can facilitate some very good encapsulation scenarios, where you can clean and declare the way to package and reuse functions.

For example, I can use an [outputcache] filter feature to output and cache my product list webpage every 30 seconds:

You can also use the [authorization] filter feature to ensure that only persons with a specific security role can edit the product:

This filtering mechanism is scalable. You can easily create your own custom filtering features for the Controller class or the action method. Filters (as well as controllers and action methods using filters) can be fully tested in units.

6) built-in HTML auxiliary methods

The first ASP. net mvc preview version has only a few html ui helper methods built into the core assembly. Then we released a separate download containing a bunch of Additional HTML helper methods that can be used for you.

The forthcoming ASP. net mvc preview version now has these built-in HTML auxiliary methods (you do not need to download them separately ). Next month, we will also begin to discuss some new improvements we are making to the ASP. NET Ajax library on the client, as well as some Ajax auxiliary methods that can be easily integrated with ASP. net mvc.

7) Many reconstruction and design improvements

The forthcoming ASP. Net MVC preview includes several refactoring and design improvements to further improve the scalability and testability of the MVC framework. In general, the development team follows this design philosophy and you have three options for all features:

1. Built-in features/implementations
2. Slightly customize the built-in features/implementations without writing a lot of code
3. Replace built-in features/implementations with custom items

With the exception, you can change the locator logic of the view engine without changing the execution logic of the view engine (and vice versa ), alternatively, you can replace the view engine completely. The Controller factory support is also extended to facilitate easy integration with the dependency injection framework. The path rules are now completely scalable, and the Controller is easier to test.

8) downloadable ASP. net mvc Framework source code (which can be compiled and applied to patches)

Last month, I announced that the source code of the. NET framework can be downloaded and debugged. After the ASP. net mvc framework is releasedSource codeThe same mechanism will also be provided to developers, just like other ASP. NET source code.

Starting from the next preview, we will also download the source code of the ASP. net mvc framework in a compiled vs project solution. This allows you to easily view and debug the source code of the ASP. net mvc framework. We will also include a license that allows you to patch the source code of the ASP. net mvc Framework, in case you encounter any defects in the application developed using the MVC framework.

This license will not allow you to re-release your supplemented ASP. net mvc version (we want to avoid the spread of multiple incompatible ASP. net mvc versions and conflicts between them ). However, it allows developers who want to Develop ASP. net mvc applications to make immediate progress without worrying about temporary defects that they cannot bypass.

Conclusion

The next ASP. net mvc preview contains many other changes (including many auxiliary attributes, methods, and objects ). We hope that the above list will provide some introduction to the coming several major improvements. During the mix conference, I will post on the preview version and provide the address of the updated preview version.

I hope this article will help you,

Scott