Changes from ASP. NET Ajax beta2 to RC

Scottgu said in his blog:

At a high-level, the changes from beta2 to RC include:

-Permission sion of a built-in VS 2005 web application project template to create new ASP. net Ajax applications. this now allows you to pick file-> new project (in addition to the existing template in file-> new web site) to create new ASP. net Ajax enabled web applications.

 

-Additional globalization support for Ajax applications, as well as additional script resource handler features to improve substitution logic, compression and caching. dynamic invocation of Web Service proxies from Javascript is also supported.

-The Assembly name of ASP. net Ajax changed from Microsoft. web. extensions. DLL to, and the namespace of the server-side features of ASP. net Ajax changed from Microsoft. web to system. web. note that the client JavaScript namespacesDid notChange (which avoids breaking existing client JavaScript code ).

The English is not very good.

From the high-level perspective, the changes from beta2 to RC mainly include:
-You can create an ASP. NET Ajax application from a VS 2005 web application project template.Program. Now, you can select a new project from the File menu to create an ASP. NET Ajax web application on a new website.

-Added global support for Ajax applications and the script resource handler feature to improve logic, performance, and cache. It also adds JavaScript to continuously and dynamically mobilize Web Services.

-ASP. NET Ajax DLL changes from Microsoft. Web. Extensions. DLL to Microsoft. Web. Extensions. dll, and the server namespace also changes from Microsoft. Web to system. Web. Note that the client-side JavaScript namespace has not changed, so do not destroy the current JavascriptCode!

He also talked about the two reasons for the Assembly set and namespace changes, so I will not translate them here.

The team made this last server namespace and Assembly change for two reasons:

1) Because ASP. net Ajax will be a fully-supported part of the core. net Framework going forward, and so for consistency it makes sense for the final release to live under the "system" namespace-which is where the other core parts of. net Framework and ASP. net live.

2) because it will help make upgrading to the "orcas" Release of ASP. net and Visual Studio much easier. ASP. net Ajax will be built-in with "orcas" (so you don't have to download and install it separately ), and by making the namespace change it means that your code will not need to change. you'll be able to optionally keep your applications running using the ASP. net Ajax 1.0 Release just fine if you want (it will run and be supported on top of orcas)-or you'll be able to change the version string in your web. config File and automatically upgrade to the newer version of ASP. net Ajax that will be encoded ded built-in to ASP. net "orcas ".