The ScriptManager Control
After this first working example, here is some more background information about how this example worked, and how the other Atlas examples throughout the book work.
The central element of an Atlas-powered ASP.NET page is the ScriptManager, <atlas:ScriptManager>. This control takes care of loading the required JavaScript libraries of Atlas, depending on which browser is used.
If you look at the resulting source code in the browser, you will see that Atlas changed very little—only the <atlas:ScriptManager> element has been replaced with this code (the undecipherable data in the URL will be a bit different on your system):
<script src="/Atlas/WebResource.axd?d=EiZ5MhryFS7wRPgWKwT3L2TYwCkaaO5mtAO5KyVbAcNmREm0baC0S _edhhqj_Y6ZuRY56z97Nu5lD2Fw5ITB3mHpybsGTsINHdsdQ_BVGi7cUBG1EWW_cWGx-I8vZeWK0 &t=632781806040000000" type="text/javascript"></script> <script src="/Atlas/WebResource.axd?d=EiZ5MhryFS7wRPgWKwT3L2TYwCkaaO5mtAO5KyVbAcNmREm0baC0S _edhhqj_Y6ZuRY56z97Nu5lD2Fw5ITB3g4TEhGZLS-_Daibixpp8tw1&t=632781806040000000" type="text/javascript"></script> <script src="atlasglob.axd" type="text/javascript"></script>
The first <script> tag is used only in non-IE browsers to add a compatibility layer; the second one loads the Atlas core library. The third <script> element contains some client-specific culture information.
Tip
When building the web application in debug mode, the JavaScript code created by WebResource.axd is nicely formatted and some errors are caught. ...