Deploying Atlas Web Site

Is it as simple as running the Atlas install? Is there a way to identify the files and include the files within our existing framework? Have Googled this and found very little in regards to deploying to a production server a Atlas enabled web site.

Thanks

PinkFloyd43 - From The Dark Side Of The Moon

Deploying an Ajax (formerly known as Atlas) website is as easy as sleeping in your bed.

The only file that you need from Ajax is the AjaxControlToolkit.dll, which you put it in your bin folder if you use it. All the other files are in the GAC of the server.

The server has to have Ajax installed. Hope that helps.

Hi. I have a similar question. I understand the need to install Ajax on the GAC and this simply means running the installer package form the Ajax site or Code plex on a production environment.

Here are some questions I have.

1. Is there any way that Ajax would NOT work if everything is installed using a Xcopy in my bin folder of the Ajax enabled web site?

2. What about security and trust levels? What is the impact of this from a deployment standpoint?

3. I assume I would not be able to install Ajax on the GAC if I have a hosted server where I host my application? What are the recommendations in this kind of a scenario?

Thanks in advance,
Sriram

I have the same doubt. Please help me out

Default atlas:UpdatePanel Default Behavior

I feel that the default behavior for an update panel should include disabling the content/controls it contains while an update is occuring (Make all the anchors turn into divs, disable all form inputs, etc.. etc..), or at least an option for toggling that functionality. Then the atlas:UpdateProgress could contain a cancel button that would re-enable the update panel's content. It seems to me that most people would expect that behavior and it would really help developers AJAX code be a little tighter.

hello.

hum...i think that you can do that by injecting javascript on the page during the events generated by the pagerequestmanager client class...another option would be to build an extender ;)

Well, I'm sure there are plenty of ways to do it; however, what I'm trying to say is it would be nice if either (A) it was the default behavior of an atlas:updatepanel while it is updating or (B) there was a property that could easily be set to accomplish this disableDuringUpdate="true" or something like that.

My reasoning is simply that I believe many people will end up writing that code themselves while one of the main goals of .NET seems to be to write less code and make it easier for a developer to produce results faster. I don't think it would be very difficult to include with the AJAX/Atlas extensions.