ASP.NET 从Beta1 升级到 Beta2 的新变化

StateBag, StateItem, and IStateManager have not changed.

         The ASP.NET persistence format of properties, collections, and templates has changed. The new format is easier to understand, more consistent, and supports a broader range of property types with our standard parsing and persisting classes. In particular:

1)       The current inner persistence format tags are no longer supported.

2)       The persistence syntax on the top level tag as it is currently done for style properties is still supported.

3)       The "inner tag" persistence of complex properties like HeaderStyle is still supported.

4)       The "inner tag" persistence of template properties as an inner XML element that matches the property name, with no namesepace prefix, is still supported. Control classes which support persistence of Template properties might not be marked InnerChildren(true). See item 6 below.

5)       The "inner tag" persistence of collection properties is still supported.

6)       Inner persistence is disabled for any control that implements the [InnerChildren(true)] attribute on the Control class. The default value for this attribute is false. When true, all nested tags will be treated as literal inner content and will not be parsed. This attribute introduces a limitation: controls that support inner children cannot also persist collection or template properties.

7)       A terse "inner tag" persistence for controls that have a single, default collection property is still supported. In order to support the terse format, the property must be marked as follows.

[PersistenceType(PersistenceMode.DefaultCollection)]

            public ListItemCollection Items { ... }

         In System.Web.UI.Web controls, the MaximumControl and MinimumControl properties have been cut from RangeValidator. RangeValidator now always uses the MinimumValue and MaximumValue properties. Use of controls or values complicated the control because two comparison inputs never needed to be used at the same time. It is common to use a Control and a Value together, but this can also be achieved using a CompareValidator.

         In the ASP.NET Configuration, web.config at the computer level was renamed computer.config. In Beta 1, all config files were named config.web. Early in Beta 2, all config files were renamed to web.config. This change renames just the web.config in the common language runtime bin directory to computer.config.

         Page.Navigate() will be removed. Instead of using Page.Navigate, page developers should revert back to using Response.Redirect() to redirect users to different pages.

         In the ASP.NET Configuration, <appsettings> and IConfigurationSectionHandler now return a NameValueCollection instead of a Hashtable / IDictionary. The IConfigurationSectionHandler interface has been changed to object Create(Object parent, ConfigurationContext confiGContext, XmlNode section);

Old Code:

IDictionary appsettings = (IDictionary)Context.GetConfig("appsettings");

Create(Object parent, IDictionary confiGContext, XmlNode section);

New Code:

NameValueCollection appsettings = (NameValueCollection)Context.GetConfig("appsettings");

Create(Object parent, ConfigurationContext confiGContext, XmlNode section);  

         System.Web.UI.Page.ClientTarget has changed from the enum type ClientTarget to a string. It is still a page directive, but it now maps to entries in the .config file that override browser sniffing if it is nonblank. The page directive should still work as before for "Uplevel" and "Downlevel" values, although they need to be changed if they were referred to in code. IsUplevel() has been removed. ClientTarget will change the results of BrowserCaps, so IsUplevel() should be replaced with a more specific check of browser caps.  

Old Code:

Page p = new Page;

p.ClientTarget=ClientTarget.Uplevel;

if (p.IsUplevel) >= 0)) {厎

New Code:

Page p = new Page;

p.ClientTarget= "Uplevel"; // Example of a browser caps check

if (p.Request.Browser.MSDomVersion.Major >= 4) {

         The System.Web.UI.Web controls.BaseValidator protected methods Convert(), Compare(), CanConvert(), and GetDateElementOrder() have been moved from BaseValidator to BaseCompareValidator. These types should not have been used.

         System.Web.HttpCachePolicy.SetEtagFromFileDependencies() has been renamed to SetETagFromFileDependencies() (capitalized ''''T'''').

         The XSP registry settings key has been changed from HKLM\Software\Microsoft\XSP to HKLM\Software\Microsoft\ASP.NET.

         HttpCacheVary is deprecated, and has been renamed to HttpCacheVaryByHeaders. HttpCachePolicy.Vary is deprecated, and has been renamed VaryByHeaders.

         The unmanaged ASP.NET binaries have been renamed from xsp* to aspnet_*.

This change will affect setup. It should not affect other code. It will affect tests using xsptool if they call

Ecbhost.Use "/", ".", "xspisapi.dll".

This can be changed to either

Ecbhost.Use "/", ".", "aspnet_isapi.dll"

or just

Ecbhost.Use "/", ".", ""

         In computer.config and web.config, the < security > section has been broken out into separate configuration sections.

Old Code:

< security > < authentication > ... < identity > ...

< authorization > ... < /security >

New Code:

< authentication > ... < identity > ... < authorization > ...

         The Config XML files (computer.config, web.config) use camel-casing for tag names. The following is a list of most tags that have been updated:

applicationEnableAuthentication

asyncOption

cpuMask

enable timeout

enableCookielessSessions

globalEnableAuthentication

idleTimeout

memoryLimit

requestAcks

requestLimit

requestQueueLimit

shutdownTimeout

sqlconnectionstring

sqlConnectionString

stateconnectionstring

stateConnectionString

userAgent

webGarden

         The BaseFile properties and AddBaseFile() methods have been removed from System.CodeDom.Compiler.TempFileCollection. These are no longer needed, since TempFileCollection no longer uses a .tmp base file.

         HtmlControls and Web controls now privately implement all methods on IPostBackDataHandler and IPostBackEventHandler. Note that, in general, these methods should not be called from outside of the ASP.NET framework.

Old Code:

myControl.LoadPostData(?

New Code:

((IPostBackDataHandler) myControl).LoadPostData(?

         ASP.NET error processing has been changed. Page.HandleError() has been replaced by the Page_Error event. Application.LastError() has been replaced by Server.GetLastError(). Use Server.GetLastError() to get the exception that was thrown (it is not passed to the function like Application.LastError() was in Page.HandleError()). Server.ClearError() has been added.

         The HttpUtility class has been modified with some renames as well as new functionality. Functions that accept/return strings previously had ToString/FromString suffixes; these have been removed.The functions that return byte[] now have a ToBytes suffix. When the encoding is missing, UTF8 is implied.

上一页  [1] [2] [3] [4] [5] [6] [7]  下一页

Copyright ＠ 2007-2012 敏韬网(敏而好学，文韬武略--MinTao.Net)（学习笔记） Inc All Rights Reserved.
闵涛 E_mail:admin@mintao.net(欢迎提供学习资源)

鄂公网安备 42011102001154号

站长：MinTao ICP备案号：鄂ICP备11006601号-18