XML webcontrol conflicts with Atlas?

hi,
I am trying to use XML control to display the xml by xsl.
Also, I would like to have the feature of no-refreshing provided by Atlas.

The followind is the simple code in my web page:

<atlas:ScriptManager ID="S1" EnablePartialRendering="true"runat="server" ><asp:button id="btn_Submit" runat="server" /><atlas:UpdatePanel ID="up1" runat="server"> <ContentTemplate> <asp:Label ID="Label1" runat="server" Text="Label"></asp:Label> </ContentTemplate> <Triggers> <atlas:ControlEventTrigger ControlID="btn_Submit" EventName="Click" /> </Triggers></atlas:UpdatePanel><asp:Xml ID="Xml1" runat="server" DocumentSource="myXML.xml" TransformSource="XMLTemplate.xsl"></asp:Xml><atlas:UpdateProgress ID="p1" runat="server"> <ProgressTemplate> <div class="progress"> <img src="images/ajax-loader.gif" />Data Loading... </div> </ProgressTemplate></atlas:UpdateProgress>

When I set the attribute of EnablePartialRendering to be false,
it would successfully display my xml data .

Is there anything I miss when using Xml webcontrol?
Or there is some other ways to fulfill my requirement?
Wish to hear some advices...Yes,there is a conflict with atlas client controls and asp.net controls.I suggest you to download the latest Atlas and try it again.Maybe it has solved the problem.
Oops...

My version was already the latest version , July CTP.

It seems that it hasn't solvd this problem yet.

So is there another way to display XML data by XSL template in the web page?

As i understand all unusual client blocks doesn't work with atlas?
When i added <IE:TEMPLATEPRINTER ID="printer"/> tag to the master page all Partial Rendering contents ceased to work.
I'm using latest version of Atlas

ok..my problem sloved.
I put XML webcontrol into another UpdatePanel of Atlas component.
It works fine now.
But I don't know why...

xmlhttp and outside servers.

I'm sure this is some kind of security feature but I'm hoping there is a fix or work around.

I have a page that is doing a xmlhttp GET to an outside server to get some data back. This works 100% when I am in debug mode in vs2008. Soon as I move the application to 1 of 2 hosting sites, it no longer works. I just get "access denied"

Why does this work just fine locally but not else where? Is there a way to around this some how?

For cross server requests, you'll need to either have an external service that supports JSONP (which is honestly kind of a pain to deal with) or create a proxy service on your local server that acts as a middle man.

but why does it work on my local server, which is a basic IIS setup and not on another server?

Different browser security settings for that local server probably.

:(

Guess I'm out of luck. I'll just run the part that needs to do the request from my local machine and everything else from the hosting.

Unless anyone has any tricks up their sleeve that can make this work :)

Thanks again ASP.Net forum people

You're not out of luck.

You just need to create a web service proxy that's running on your local domain. Basically an asmx in your solution that basically does no more than call the remote service and then return that result. So, your client side functionality can call the remote service by calling the local one, and there are no cross domain issues.