ajax beta 1.0 run well in firefox 2.0 , but does not work in IE6 SP1 (winXp or win2000)

I migrate my company website form atlas to ajax beta 1.0 ,but there are script erros in IE6 SP1 (winXP or win2000) when I call web serviece from javascript.the

win2000 OS is updated to SP4 and the winXP OS is updated to SP1,but ajax does not run. when some winXP pc OS is updated to SP2,ajax run well.

By compared, ajax run well in firefox 2.0.

there are many IE users who need my help to run my website ,but who can help me?

Hi,

ASP.NET team member, Chris Riccio has pointed that this problem maybe be caused by a bug in IE 6 SP1 concerning to HTTP compression. In fact, I was able to fix it installing the patch KB912812 on the clients.

AJAX and WebApplication Project Type

I have a VS2003 Web project I converted to VS2005 sp1 WebApplication project (not WebSite project). I wanted to add AJAX to this web application so I followed the directions outlined in the video on the AJAX site. I added all the entries to the web.config without any trouble. I added the ScriptManager control to one of the pages and an UpdatePanel. I also had to set a reference tosystem.web.ui. System.Web.Extensions However, when I try to drag some of the asp.net controls already on the page (drop down boxes) to the update panel, it does not seem to be accepting them. They are not "dropping into" the update panel. The panel does not highlight when I drag the controls over it.

What am I missing?

EDIT: The reference I set was System.Web.Extensions...not web.ui.

Apart from working with the Designer, have you tried working around in the HTML to see if its working?

Wrap your controls with the UpdatePanel and see if the page is working.

-Thanks

It's hard to tell without seeing the web.config, etc. The easiest way (and the method I used) is to create a new project, and view the differences between the web.config files and references.

I copied all of my project-specific settings (the ones that I added myself) to the web.config for the new project, then copied the resulting file to my actual upgraded project. It worked for me!

Just be sure to make backup copies of the old web.config, just in case you need to revert.

ravivb.net:

Apart from working with the Designer, have you tried working around in the HTML to see if its working?

Wrap your controls with the UpdatePanel and see if the page is working.

-Thanks

I have not tried that appraoch yet, however I will give it a try. thank you for your response.

ps2goat:

It's hard to tell without seeing the web.config, etc. The easiest way (and the method I used) is to create a new project, and view the differences between the web.config files and references.

I copied all of my project-specific settings (the ones that I added myself) to the web.config for the new project, then copied the resulting file to my actual upgraded project. It worked for me!

Just be sure to make backup copies of the old web.config, just in case you need to revert.

I will give this a try. I originally did it the other way around (copied web.config entries from the emtpy project to my project). Thank you for the response.

wjdunn3:

ravivb.net:

Apart from working with the Designer, have you tried working around in the HTML to see if its working?

Wrap your controls with the UpdatePanel and see if the page is working.

-Thanks

I have not tried that appraoch yet, however I will give it a try. thank you for your response.

This approach worked. I added the Script Manager and Update Panel to the Page then switched to HTML view. I moved the Script Manager tags to be just under the first FORM tag. I wrapped the code I wanted in the Update Panel tags and *important part* ContentTemplate tags.

I don't know why it does not work within the designer...I will have to try and figure that out another day. Thanks all for the quick responses.