AspNet
MVC2_RC_VS2008.exe
ASP.NET MVC 2 Release Candidate Release Notes
This document describes the Release Candidate release of the
ASP.NET MVC 2 framework.
Installation Notes 2
Documentation 2
Support 2
Upgrading an
ASP.NET MVC 1.0 Project to
ASP.NET MVC 2 2
New Features 3
ASP.NET MVC validation scripts have been moved to their own file 4
ASP.NET MVC validation scripts can be included at the top or bottom of a page 4
ASP.NET MVC validation scripts support globalization 4
Html.ValidationSummary helper method can display model-level errors 4
T4 templates in Visual Studio generate code that is specific to the target version of the .NET Framework 4
Other Improvements 4
Bug Fixes 5
Breaking Changes 5
Changes in
ASP.NET MVC 2 Release Candidate 5
Changes in
ASP.NET MVC 2 Beta 6
Changes in
ASP.NET MVC 2 Preview 2 6
Changes in
ASP.NET MVC 2 Preview 1 7
Known Issues 7
Disclaimer 8
This document describes the Release Candidate release of
ASP.NET MVC 2 for Visual Studio 2008 SP1.
Installation Notes
The
ASP.NET MVC 2 Release Candidate for Visual Studio 2008 SP1 can be downloaded from the following page:
http://go.microsoft.com/fwlink/?LinkID=157071
ASP.NET MVC 2 can be installed and can run side-by-side with
ASP.NET MVC 1.0.
Note Because Visual Studio 2008 and Visual Studio 2010 Beta 2 share a component of
ASP.NET MVC 2, installing the
ASP.NET MVC 2 Release Candidate release on a computer where Visual Studio 2010 Beta 2 is also installed is not supported.
Documentation
Documentation for
ASP.NET MVC 2, which includes tutorials, technology overviews, code samples, and API reference, is available on the MSDN Web site. A good starting point is the
ASP.NET Model View Controller (
MVC) topic (http://go.microsoft.com/fwlink/?LinkId=159758).
Tutorials and other information about
ASP.NET MVC are also available on the
ASP.NET Web site (http://www.
asp.net/
mvc/).
Support
This is a Release Candidate (RC) release and is not officially supported. If you have questions about working with this release, post them to the
ASP.NET MVC forum (http://forums.
asp.net/1146.aspx), where members of the
ASP.NET community are frequently able to provide informal support.
Upgrading an
ASP.NET MVC 1.0 Project to
ASP.NET MVC 2
To upgrade an existing
ASP.NET MVC 1.0 application to version 2, follow these steps:
Make a backup of the existing project.
Open the project file in a text editor (the file with the .csproj or .vbproj file extension) and find the ProjectTypeGuid element. As the value of that element, replace the GUID {603c0e0b-db56-11dc-be95-000d561079b0} with {F85E285D-A4E0-4152-9332-AB1D724D3325}. When you are done, the value of that element should be as follows:
<ProjectTypeGuids>{F85E285D-A4E0-4152-9332-AB1D724D3325};{349c5851-65df-11da-9384-00065b846f21};{fae04ec0-301f-11d3-bf4b-00c04f79efbc}</ProjectTypeGuids>
In the Web application root folder, edit the Web.config file. Search for System.Web.
Mvc, Version=1.0.0.0 and replace all instances with System.Web.
Mvc, Version=2.0.0.0.
Repeat the previous step for the Web.config file located in the Views directory.
Open the project using Visual Studio, and in Solution Explorer, expand the References node. Delete the reference to System.Web.
Mvc (which points to the version 1.0 assembly). Add a reference to System.Web.
Mvc (v2.0.0.0).
Add the following bindingRedirect element to the Web.config file in the application root under the configuraton section:
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.
Mvc"
publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0" newVersion="2.0.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
Create a new
ASP.NET MVC 2 application. Copy the files from the Scripts directory of the new application into the Scripts directory of the existing application.
Compile the application and run it. If any errors occur, refer to the Breaking Changes section of this document for possible solutions.
New Features
This section describes features that have been introduced in the
ASP.NET MVC 2 Release Candidate release.
ASP.NET MVC validation scripts have been moved to their own file
To help reduce conflicts with other Ajax libraries, the built-in
ASP.NET MVC validation scripts are now in a separate JavaScript file.
ASP.NET MVC validation scripts can be included at the top or bottom of a page
The server component that renders the client validation metadata now renders the metadata into a JavaScript variable. This allows the validation scripts to be included either at the top of the page or at the bottom, because the scripts will look for the variable and load the metadata when it is available.
ASP.NET MVC validation scripts support globalization
When the required
ASP.NET Ajax globalization scripts are included in a page, the validation logic uses the culture-specific data for data types (such as dates and numbers) when it validates input text. The new Html.GlobalizationScript helper method can be used to render a reference to the globalization script for the current culture.
Html.ValidationSummary helper method can display model-level errors
Instead of always displaying all validation errors, the Html.ValidationSummary helper method has a new option to display only model-level errors. This enables model-level errors to be displayed in the validation summary and field-specific errors next to each field.
T4 templates in Visual Studio generate code that is specific to the target version of the .NET Framework
A new property is available to T4 files from the
ASP.NET MVC T4 host that specifies the version of the .NET Framework that is used by the application. This allows T4 templates to generate code and markup that is specific to a version of the .NET Framework. In Visual Studio 2008, the value is always .NET 3.5. In Visual Studio 2010, the value is either .NET 3.5 or .NET 4.
Other Improvements
The following additional changes have been made to existing types and members for the
ASP.NET MVC 2 Release Candidate release.
The default HTML markup that is generated by the Add View dialog box has been changed to be consistent with the markup that is rendered by the templated helpers (Editor, EditorFor, Display, and DisplayFor).
Buttons in a form can specify that they do not cause validation logic to run. The default is that every button in a form causes validation logic to run, and if validation fails, the validation logic blocks submission of the form. Enabling validation selectively for buttons lets you create forms that can post information even if a form is not complete or if the form contains data that is temporarily invalid.
Client validators can specify when they run. Possible values are input (while the user is typing), blur (after the user is done typing and moves to another field), and submit (when the user submits the form).
Bug Fixes
The following bugs have been fixed in the
ASP.NET MVC 2 Release Candidate release.
The FileResult action result now supports non-US-ASCII characters in file names.
Methods and properties of the TempDataDictionary class have been improved to better handle the case when items are flagged for removal from the dictionary.
Support for validation in the IDataErrorInfo interface has been fixed.
Breaking Changes
The following changes might cause errors in existing
ASP.NET MVC 1.0 applications.
Changes in
ASP.NET MVC 2 Release Candidate
IIS script mapping script is no longer available in the installer
The IIS script mapping script is a command-line script that is used to configure script maps for IIS 6 and for IIS 7 in Classic mode. The script-mapping script is not needed if you use the Visual Studio Development Server or if you use IIS 7 in Integrated mode. The scripts are available as a separate unsupported download on the
ASP.NET CodePlex site.
The Html.Substitute helper method in
MVC Futures is no longer available
Due to changes in the rendering behavior of
MVC view engines, the Html.Substitute helper method does not work and has been removed.
Changes in
ASP.NET MVC 2 Beta
The IValueProvider interface replaces all uses of IDictionary<string, ValueProviderResult>
Every property or method argument that accepted IDictionary<string, ValueProviderResult> now accepts IValueProvider. This change affects only applications that include custom value providers or custom model binders.
Examples of properties and methods that are affected by this change include the following:
The ValueProvider property of the ControllerBase and ModelBindingContext classes.
The TryUpdateModel methods of the Controller class.
New CSS classes were added in the Site.css file that are used to style validation messages.
Changes in
ASP.NET MVC 2 Preview 2
Helpers now return an
MvcHtmlString object
In order to take advantage of the new HTML-encoding expression syntax in
ASP.NET 4, the return type for HTML helpers is now
MvcHtmlString instead of a string. Note that if you use
ASP.NET MVC 2 and the new helpers with
ASP.NET 3.5, you will not be able to take advantage of the HTML-encoding syntax; the new syntax is available only when you run
ASP.NET MVC 2 on
ASP.NET 4.
JsonResult now responds only to HTTP POST requests
In order to mitigate JSON hijacking attacks that have the potential for information disclosure, by default, the JsonResult class now responds only to HTTP POST requests. Ajax GET calls to action methods that return a JsonResult object should be changed to use POST instead. If necessary, you can override this behavior by setting the new JsonRequestBehavior property of JsonResult. For more information about the potential exploit, see the blog post JSON Hijacking on Phil Haack’s blog.
Model and ModelType property setters on ModelBindingContext are obsolete
A new settable ModelMetadata property has been added to the ModelBindingContext class. The new property encapsulates both the Model and the ModelType properties. Although the Model and ModelType properties are obsolete, for backward compatibility the property getters still work; they delegate to the ModelMetadata property to retrieve the value.
Changes in
ASP.NET MVC 2 Preview 1
Changes to the DefaultControllerFactory class break custom controller factories that derive from it
The DefaultControllerFactory class was fixed by removing the RequestContext property. In place of this property, the request context instance is passed to the protected virtual GetControllerInstance and GetControllerType methods. This change affects custom controller factories that derive from DefaultControllerFactory.
Custom controller factories are often used to provide dependency injection for
ASP.NET MVC applications. To update the custom controller factories to support
ASP.NET MVC 2, change the method signature or signatures to match the new signatures, and use the request context parameter instead of the property.
“Area” is a now a reserved route-value key
The string “area” in Route values now has special meaning in
ASP.NET MVC, in the same way that “controller” and “action” do. One implication is that if HTML helpers are supplied with a route-value dictionary containing “area”, the helpers will no longer append “area” in the query string.
If you are using the Areas feature, make sure to not use {area} as part of your route URL.
Known Issues
Adding a debugger watch that shows a value from TempData will mark it for deletion. The side effect was introduced as part of the changes to TempDataDictionary.
Disclaimer
This is a preliminary document and may be changed substantially prior to final commercial release of the software described herein.
The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.
This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.
Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, email address, logo, person, place or event is intended or should be inferred.
© 2009 Microsoft Corporation. All rights reserved.
Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.
7559
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
