I'm confused on a number of issues about the AutoLoad I understand the IFrame mode, but the 'merge' mode with a local page is very confusing as to what the rules are. For example, in the 'merge' mode:

- The .aspx page cannot have a <form>, so its really just an html snipit not a real page.
- If you put the Coolite Controls on an AutoLoad aspx page, it says that the ScriptManager is missing. Adding the ScriptManager allows it run, but none of the Coolite controls render. (I tried the ScriptMangerProxy, but nada)

So the first question is:
- CAN THE COOLITE CONTROLS BE USED IN AN AUTOLOAD PAGE? If so, how.

The Second issue is more of a design issue or discussion:

I'm the one that suggested the 'AutoLoadIFrame' feature in the first place, however now that I play with this some more, it seems another scenario may be more approprite. What if all .aspx pages were rendered in IFrames, and local .ascx User Controls were rendered in 'merge' mode. This is what User Controls do, 'merge' their code under a parent on the server side. This way the User Control Template model would be more consistent between client and server models.

I'm upgrading a product that makes extensive use of IFrames on the client side, and ITemplate.InstantianteIn() modules (like User Controls) on the server side to do similar injection into a page. I'm thinking that this AutoLoad can replace some of the IFrames and get better overall page integration and responsivness. But I'm begining to have second thought after not being able to get it working in a week or more of work.

Also, I still have other related unresolved posts regarding sizing and client side AutoLoads:

http://forums.ext.net/showthread.php...4141-16-1.aspx
http://forums.ext.net/showthread.php...4082-16-1.aspx

- Frustrated