The central element of an Atlas-powered ASP.NET page is the
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> 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.
<atlas:ScriptManager ID="ScriptManager1" runat="server"> <Scripts> <atlas:ScriptReference Path="MyScript.js" /> </Scripts> </atlas:ScriptManager>
If you are using ASP.NET 2.0 master pages and most of your pages use the Atlas framework, you may consider putting the
ProxyID="ScriptManagerProxy1" runat="server"> <Scripts> <atlas:ScriptReference Path="MyScript.js" /> </Scripts> </atlas:ScriptManager
This was just the first step; there’s more to come in the following chapters!