16.3. Using a Different Platform
The Microsoft AJAX Library is available in a standalone zip file. It includes the scripts that are sent down to the browser to enable AJAX functionality. You can deploy these files to any Web server on any platform. As already discussed, script files are not versioned like a binary file is, so the zip file includes a path with version information. If you follow this convention when deploying the files, you can easily migrate to a new version of the AJAX Library when it becomes available. The versions are backward compatible, so you can also run one version of scripts alongside a newer version if some new behavior or change requires updating code. This versioning is helpful in making it easy to switch between versions after validating functionality and features. This is particularly useful in ensuring a smooth transition when updating an existing application with features found in a new release.
When it comes to deployment, if you aren't using any of the server features of ASP.NET AJAX, you could just put the Microsoft AJAX Library JavaScript files on the server and have them downloaded to the browser.
The three library files all come in release and debug versions:
The release also includes a large set of files in a Globalization subdirectory for greater reach. Localized versions of error messages and warnings are included to facilitate better and more accurate feedback for the user. In the first version of ASP.NET AJAX, there was also a pid.txt file, which included licensing information you were required to provide if you called in to Microsoft support with a question. After that release, the features were incorporated directly into the .NET Framework, and the separate pid.txt file was no longer necessary.
The ASP.NET team has validated the functionality on Internet Explorer, Firefox, Safari, and Opera browsers. The team is usually testing against the latest released versions and working on the beta versions.