ASP. NET 2.0 Ajax beta 2 Release Notes

ASP. NET 2.0 Ajax beta 2 Release Notes (translated from this document) 1 . Release descriptionThis document describes the differences between Ajax beta1 and beta 2. Microsoft ASP. NET Ajax 2.0 extension is the new name of ASP. NET Ajax technology. If you want to provide suggestions, go to the Ajax discussion and suggestion forum to share your views. This release file mainly includes the core framework of the client, the client class system, the http post and get network methods called through the stack, scriptmanager, updatepanel, and updateprogress controls are also added to ASP from the CTP version. NET 2.0 Ajax. The Ajax CTP version provides more functions, but it is still under development. You can download this version here 2 . Installation instructionsRun aspajaxextsetup directly. install the MSI file and run the following command to install the file: siexec/I aspnetajax. msi [/q] [/log <logfilename>] [installpath = <installation path>]-<logfilename> is the path name of the log that can be selected-<installationpath> is an optional installation path 3 Notes between two versionsThe prefix is changed from <Atlas:> to <asp:>. The prefix name must be changed from Microsoft. web. atlas. DLL is changed to Microsoft. web. extensions. DLL, the new assembly is strongly named, and is loaded into the GAC Cache during installation, you no longer need to reference the original assembly in the project bin folder in visual studio.net 2005 team version. In the Add reference dialog box project, no Microsoft. web. extensions program component. However, this situation does not occur in other vs versions. To solve this problem, we can. manually Add a reference to the config file: 1. create a new registry entry HKEY_LOCAL_MACHINE/software/Microsoft /. netframework/assemblyfolders/asp. net ajax1.0.610252. set the key value to include Microsoft. web. extensions. the physical path of the DLL Assembly, rather than the environment variable, such as: % ProgramFiles %. If it is installed on drive C by default, the path will be: C:/program files/Microsoft ASP. net/asp. NET 2.0 Ajax extensions/v1.0.61025 in Beta 2, The prerender methods of extendercontrol and iscriptcontrol on the near server end no longer work, so the client instance script will generate the following error: reference a nonexistent DOM object 4. Differences between the two editionsFixed Multiple bugs and introduced new features. These changes may affect your previous code. 4.1: the huge change adds scriptresource handler, but it must be in the web. add the following items to config: <add verb = "get" Path = "scriptresource. axd "type =" Microsoft. web. handlers. scriptresourcehandler "Validate =" false "/> If the web. if the config file does not exist, the following error occurs: 'sys 'does not define extendercontrol. The iextendercontrol and iscriptcontrol classes must be registered in sys with scriptmanager in their prerender events. UI. the key enumeration renames the keyword that conflicts with Js. Use del instead of delete, and use enter instead of return to all the static APIs of array. prototype to avoid potential conflicts with other customer frameworks. For example,. add ('added') becomes array. the attributes under add (A, 'added') are changed from virtual to non-virtual: profileservicemanager. path authenticationservicemanager. pathupdatepanelcontroltrigger. controlid 4.2 partialrendering: updatepanel, scriptmanagerAdded the supportspartialrendering attribute in scriptmanager. By default, this attribute determines whether local refresh is supported based on the httpbrowsercapabilities value of the browser. If false is returned, no matter how the client sets this value, all callback calls in partial refresh will return the page scriptmanager as normal. setfocus allows you to conveniently set the focus in updatepanel and add scriptmanager. registerdispose, which allows the updatepanel control to maintain the client image for release during partial page refreshing without generating DOM object exceptions. 4.3 Client frameworkFor more information about the core framework, see section 4.1. You can add Dom multi-event handles in an operation without creating a proxy. You can use $ addhandlers or sys. UI. domevent. addhandler. by calling $ clearhandlers (or sys. UI. domevent. clearhandlers) to remove the event handle added through the domevent API, which simplifies the operation logic. add an optional parameter to parse: Case Sensitive, sys. UI. key. parse ("Del", true) Changes in regionalization: Added the enableclientscriptglobalization attribute in scriptmanager. The default value is false. For upcoming requests, scriptmanager will generate a built-in SYS. cultureinfo. currentculture type. This will be based on the upcoming request and the rewriting of page developers in SYS. cultureinfo. string is added under currentculture. localeformat, date. localeformat, number. the localeformat method is in SYS. cultureinfo. the string is added to invariantculture. format, date. format, number. format Method Changes in LocalizationThe original dynamic Script Reference obtained through the built-in Web resource is now provided by the server-side scriptresource handle. The enablescriptlocalization attribute is added to scriptmanager in the web. config file to replace the scriptresource handle that calls the ASP. NET 2.0 webresource handle. The default value is false. when it is set to true, scriptmanager will reference each script, including the localized operation scriptresource handle, to provide the script reference for the class library and append the localized JS Resource Type Static, the script library of basic text can be used for localization. Page developers can use the scriptreference. resourceuicultures attribute to detect available UI localization values. About Debug. Trace And Debug. Dump ChangesDevelopers can output stack information to the text box called traceconsole, in the script debugger, or in the firebug console, developers can make full use of DEBUG. Dump. Improved Script LoadingThe client framework uses the queue model to load or reference scripts in sequence. The built-in <SCRIPT src = ""> label is no longer required for scripts to define components and page developers when creating script class libraries registered through the scriptmanager control, A small piece of code should be included in the class library to indicate whether the class library has been loaded by the client. Not all browsers need to do this, but for Safari, This is required so that it can dynamically load the script and add the scriptloadtimeout attribute to scriptmanager, to indicate the time required for the referenced script to be loaded to the local client sys. application will trigger a series of new events, such as loading timeout and loading failure sys. applicationloadeventargs sets a get_ispartialload attribute to check whether the current client is in partial refresh mode. 4 . 4 Network and program servicesWhen sys. services. authenticationservice. when logout is successfully completed, it will always perform the redirection operation. Originally, the redirection will be performed only when the URL is specified (if there is no URL, it will be directed to this page) sys. services. authenticationservice. both login and logout call the specified completion callback event, and even when page redirection occurs, it will execute. Previously, the callback event will be skipped in the web. in config <profileservice> configuration item, <configuration> <Microsoft. web> <scripting> <WebServices>:-The getproperties property calls the readaccessproperties method. The setproperties property calls the writeaccessproperties method. 4.5 Other changesThe design class is moved to Microsoft. Web. Extensions. Design. dll.

(Translated from Ajax extension beta 2 release note. For the original content, see release notes for ASP. NET 2.0 Ajax extensions beta 2. For horizontal reasons, the translation may contain errors or inaccuracies. Please criticize and advise!