how do I develop an Atlas application?

Hi

I have been developing asp.net applications for a couple of years now and am trying to get my head around this atlas/ajax thing.

If I was to build an application of say 20 .aspx pages I would know exactly how to go about it but I am a bit stumped on how to start an Atlas enabled one that is maintainable in a logical manner.

Instead of seperate aspx pages, do I use a user control for each "page" instead and make ajax call backs from a single page?

I can follow the examples on the Atlas website but they tend to contain only a little bit of functionality on each page - is this the way that most people are using it?

Are there any online documents that describe best practices for architecting a decent sized application using Atlas?

Any help or direction pointing would be appreciated.

cheers

Yes, I'm still organizing my sites into logical pages with atlas being used to update sections of the page dynamically, but the same principles hold true with normal asp.net functionality. You wouldn't create a site with only one asp.net page and try to handle all your functionality within just that one page with showing/hiding placeholders and event handlers for all your events. (At least I wouldn't!) I don't think you'd do the same with atlas. At some point you're going to want to load a new page, and that involves communicating with the server. I think there's only so much you want the client/surfer's PC doing - some things are better/safer when handled on the server and the resulting html returned to the client browser. It depends on your needs and what you're trying to do. That's just my .02.

(Plus you can't have an updatepanel inside a template, like a repeateritem, (yet :), so that really limits alot of what you can do anyway within just one aspx page)

i have worked on application which involves team management and it was round abt 20 pags app. We have put ajax on main pages like tasks list, billing pages and hours tracking page. Rest of the site, which involves add,edit ,delete such as for users ,projects etc ; we have used normal post back.

Dont design ur web app like a win app, with one form and many user controls. This will cause head ache in future.

ok thanks for that guys.

that actually helps a lot - I was getting myself confused with what was "possible". It looks like performance is still king in asp.net