ASP. NET Ajax 1.0 RC version released

[Original address] ASP. NET Ajax 1.0 Release Candidate now available
[Original article publication date] Friday, December 15,200 6 AM

Earlier today, the ASP. NET development team launched the RC (candidate release) version of ASP. NET Ajax 1.0. This is the penultimate release of ASP. NET Ajax. The next public release will be the final, fully supported 1.0 products.

Compared with beta2, this candidate release version includes several new features and a major change. Here you can read a document listing all the changes from CTP> beta1> beta2> RC. In general, changes from beta2 to RC include:

-Includes a built-in VS 2005 web application project template to create an ASP. NET Ajax application. This allows you to create a web application that enables ASP. NET Ajax through a File> A new Project (except a File> an existing template in a new website.

-The additional globalization support for Ajax applications, as well as other script resource processor features to improve the replacement logic, compression, and cache. Dynamic Web Service proxy calling in Javascript is also supported.

-Asp. net Ajax Assembly name from Microsoft. web. extensions. change DLL to system. web. extensions. DLL, Asp.. Net Ajax server features from Microsoft. the Web is changed to system. web. Note: The client-side JavaScript namespaceNoChanges to avoid invalid JavaScript code on the client.

There are two reasons why the developer makes the last namespace and Set Name Change:

1) Because ASP. net Ajax will become the core in the future. A fully supported part of the. NET Framework. For consistency consideration, it is reasonable that the final release is under the system namespace, because the system namespace is another core. net Framework and ASP.. net.

2) It makes it easier to upgrade to the next-generation ASP. NET and Visual Studio products codenamed orcas. ASP. NET Ajax will be built into orcas (so you don't need to install it separately/download). The change in namespace now means that your code will not need to be changed in the future. If you need it, you can also choose to continue running your application in ASP. NET Ajax 1.0, which is no problem because ASP. NET Ajax 1.0 will be able to run on Orcas. Alternatively, you can change the version string in your web. config file and automatically upgrade it to the new ASP. NET Ajax version included in the built-in ASP. NET orcas file.

This White Paper provides instructions on how to upgrade existing ASP. NET Ajax beta2 applications to ASP. NET Ajax RC.

Important intelliisense tips:

After completing the steps in the preceding whitepaper, You need to delete the schema cache file that identifies intelliisense with the control maintained by. This ensures that the intelliisense provided by your HTML editor for the ASP. NET Ajax control appears and is correct. Otherwise, it may still use the values in the previous beta2 version.

-In Windows XP, you only need to deleteC:/document and settings/[yourusername]/Local Settings/appdata/Microsoft/visualstudio/8.0/reflectedschemasAll the files in this folder can be used.

-In Windows Vista, you only need to deleteC:/users/[yourusername]/appdata/Roaming/Microsoft/visualstudio/8.0/reflectedschemasAll the files in this folder can be used.

Delete these schema files. After you restart vs, it recalculates the intelliisense of the HTML logo for all controls to obtain changes caused by changes in the Set Name.

I hope this article will help you,

Scott