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 without web services.

All the examples I have seen on Atlas uses web services. I want to use regular aspx methods instead. Is it possible to write an Atlas application that for every 5 seconds call a method in a regular aspx file to check for changes and based on the result of the method updates only a part of a page? Can anyone show some example code?I figured this out. Sorry for bothering you.

hello.

just one more thing: don't forget that page methods are really expensible...if you can, use a web service method to check the update condition.

I have seen both ways and I noticed using web services are more emphasized.

Why are using web services any quicker ?

Atlas problem with page base class structure

Hi there,

I'm working on a ASP.NET 1.1 application that was converted to 2.0. Instead of using master pages and templates in uses inherited base page classes to ensure consistancy of look, feel and functionality across all the pages.

The base class from which all pages inherit builds the html structure of the page. All that's in aspx page is:

<%@dotnet.itags.org. Page language="c#" Inherits="F360.PresentationTier.Testing.AJAX" CodeFile="AJAX.aspx.cs"%>
<head runat="server" id="headTag" />

CodeBehind is:
public partial class AJAX : BasePageHtmlAndNav

When creating pages the developer can drop in controls into the aspx page but the headers, footers, structure and menus etc are all built by the base page in OnInit

Ok, on to my ATLAS issue:

I've tested a simple updatePanel using a standard WebForm template and it works great. However when I try to add a ScriptManager and UpdatePanel to a page derived from our base class structure described above the updatePanel doesn't update. An asynchronous postback is made and the server-side event is triggered but the contents of the panal doesn't change.

I know it's hard to fathom what's going on here without full details of our base page class structure but if anyone has any ideas I'd appreciate it as I'm very keen to integrate the ATLAS framework in future applications that we'll be developing here.

Many thanks

MatOk, having read some posts on ATLAS problems with Master pages I did some tinkering and found the strangest (to me) of issues. ATLAS works fine with the base class structure outlined in my previous if there are no linked style sheets in the <head> tag. As soon as I add a style sheet (dynamically) to the head tag at runtime (as a LiteralControl) the updatePanel does not refresh. Does anyone have any idea why tis might be?

N.B. It makes no difference what is in the stylesheet. The problem still occur even when the links style sheet is empty.

Thanks

Mat

hello.

well, i'd say that you're generating a non valid xml element, ie, you're probably not closing the html element that is being sent to the browser. you can easilly verify this by using fiddler. what you must know is that, currently, the contents of the head section (if you have it with runat="server") are sent inside an xml message generated by the server in response to a partial postback and they aren't eascaped by using a cdata section. so, it's important to make sure that the contents of the head element are well formed xml elements.

btw, the correct way to identify a stylesheet to the page is to sue the htmllink element:

HtmlLink link = new HtmlLink( );
link.Href = "caminho ate Css file";
link.Attributes.Add( "rel", "stylesheet" );
link.Attributes( "type", "text/css" );
this.Header.AddParsedSubObject( link );

Hi there,

Thanks for the info. You were spot on. One of the style tags wasn't closed and when I corrected that worked... kind of!

The first postback is fine. However on the second postback I get the following error and IE crashes:

Unhandled exception at 0x7dd47bb3 in IEPLORE.EXE: 0xCOOOOOO5:
Access violation reading 0x0000004

Any ideas anyone?

And thanks for the tip regarding stylesheet link. I'll sort that out.

Mat

hello.

can you test that in another browser? it may be a problem with your ie...

Thanks for you're assistance. I got to the bottom of it in the end. I doubt anyone else will have a similar issue but I'll outline it anyway.

The application I'm working on used a CSS unorder list dropdown menu, as descibed here:http://www.tanfa.co.uk/css/examples/menu/tutorial-v.asp

To make the menu work correctly in IE an htc behaviour had to be attached to the body tag in the stylesheet. It was this beahviour that was causing IE to crash when asynchronous calls were being made. (No idea why). When I removed the behavious ATLAS worked fine. I have since changed the very light CSS menu for a third party control and now have both ATLAS functionality and a funky new menu. All good.

Thanks again

Mat

Can you explain better the solution...?
I have exactly the sameproblem... and I use a similar menu fromWebFX and I followed your linkbut I don't understand what's the problem generating the crash muchless the solution proposed...

Thanks
Agapito