<atlas:ScriptManager ID="ScriptManager1" runat="server" >
<atlas:ScriptReference ScriptName="AtlasUIDragDrop" />
you will not be able step into any of the ATLAS libraries you happen to be using as the debugger complains that the source files are not available. This is because of the way the ATLAS scrip manager embeds the java script.
today I found myself thinking that it would be handy to be able to step into these files to find out what's going on prior to the error.
To solve the problem
- Copy the necessary java script files from the install location into your project and mark them as "Embedded Resource". In my case Atlas.js and AtlasUIDragDrop.js
- Comment out or remove the Atlas Script Manager component
- Add the script files as you would add any normal java script file (ie with the <script> tag)
Once you have done this you should be able to step into the ATLAS java script files to your hearts content, but be warned you might find it a little scarey in there.
The only problem with this is that it won't work for Server Side Atlas controls, such as UpdatePanel or Extender controls, but if you're not using them, or if you can comment them out while you debug stuff, then you're set.