Atlas wont work on server

Hello.

I uploaded all my files in my atlas projekt to the server.

Now it won't work at all. everytime the atlas shoud change something instead of reload the page the page is reloaded.

On my local machine this is not any problem, and the atlas.dll file is in the bin filer so i do not think thats the problem.

Any Idea?

Thanks

Hi,

just a guess here but did you change the web.config to state that debug="false" on your server? If not try that option (you can change it in the web.config file). I read that the Atlas assembly regenerates other pointers to the resources for every request when in Debug mode.

Grz, Kris.

XIII:

Hi,

just a guess here but did you change the web.config to state that debug="false" on your server? If not try that option (you can change it in the web.config file). I read that the Atlas assembly regenerates other pointers to the resources for every request when in Debug mode.

Grz, Kris.

No that dident work ..

But thanks for the answer :D

Any other idea??

I think you have to install Atlas in the Server for it to work, not just the .dll

mrmercury:

I think you have to install Atlas in the Server for it to work, not just the .dll

Normally the deployment of the needed assembly to the /bin subfolder should suffice.

Grz, Kris.

hello guys.

besides adding the dll, you might also need to register the asbx extension used by brigdes. however, i think that this is not the problem you're having. have you configured your web site to use asp.net 2.0?

Luis Abreu:

hello guys.

besides adding the dll, you might also need to register the asbx extension used by brigdes. however, i think that this is not the problem you're having. have you configured your web site to use asp.net 2.0?

Yes my server have asp 2 and i have also installed atlas on the server.

The site is working exept atlas so its must be a config error i think.

Thanks for answering.
I'm having problems getting a simple Atlas Updatepanel on my server too.
I've got the Microsoft.Web.Atlas.dll in the ASP.NET Bin folder, copied the Web.config from a new website created using the Atlas template.

I've got a page with a dropdownlist and a gridview with a load of template fields (the gridview's SqlDataSource has a controlparameter for the dropdown's SelectedVale). I added a Scriptmanager and wrapped the gridview in an Updatepanel (and a contenttemplate). I added an UpdateProgress control and a trigger:

<Triggers>
<atlas:ControlValueTrigger ControlID="dropdownlist1" PropertyName="SelectedValue" />
</Triggers
(I also tried a ControlEventTrigger with "SelectedIndexChanged"). I've tried changing the list autopostback = false, debug=false in the web.config and checking that the legacy tag isn't in the webconfig

The page runs exactly the same as without the Scriptmanager and the UpdatePanel (except for a label I have outside of the Updatepanel is now only visible during updates, and the UpdateProgress control being visible during updates). It doesn't produce any errors, but it is still posting back. It's driving me nuts! Am I missing something obvious?

Any help much appreciated!
huum maybe I also have to publish my code :d

I did the Scott todolist and thats the one that do not work..

CODE:

Status:

Ferdige
Ikke gjort

Oppdaterer...

Innhold

/CODE

Sorry but some of the text is in norwegian..
Hello.

It works now.. I had to restart the server and then its up and running.

So thanks so much

Atlas script files

I have page, which shouldn't be cached. So, I have the following statement on my page_load event:

Response.Cache.SetCacheability(

HttpCacheability.NoCache);

As it seems is that also all atlas script is not cached on the client because of that.
Is there any workaround?

I'm using only update panel on my page. How can I reduce the size of atlas script to only those needed for update panel?

I have 2 updatePanels on my page and because of that, page generates 2 axd script files:

WebResource.axd
WebResource1.axd

Can I reduce that?

Thank you for your answers,

Simon

Actually, the behavior you are observing is the most optimal way possible to handle things when it comes to the UpdatePanel. Because the references to the necessary scripts are linked using the Web Resource method, the browser will cache the content obtained from those .axd resources by default (I am sure you can change this on most browsers if you want). This will occur whether you are caching content on the server or not.

In addition, the script returned from those web resource URL's are optimized for minimal size in transmission, so there is not really anything more to do as an optimization other than to using similar methods to customize your own Javascript to accomplish the same tasks.

In my experience, the browser (IE6) does not cache the Atlas scriptfiles which are retrieved using the WebResource method. When I retrieve an Atlas driven page, all Atlas AXD files are downloaded, When I retrieve this Atlas page again (using the same hyperlink), the files are downloaded again. Because of the filesizes, the page loads very slow on low bandwith lines.

Does anybody have a clue how to use the browser cache for the Atlas files, so the only have to be loaded one time?

Regards, Ad

Hi,

areijngoudt, did you check if debug="false" in your web.config? Having debug="true" prevents web resources from being cached in the browser.