I have never gotten an UpdatePanel to work. Obviously everyone else is getting them to work, but not me. 

1) I'm running the latest Atlas Beta. I have uninstalled and reinstalled. It's not that.
2) I started with the Atlas web.config and put my previous web.config customization back into it.
3) I have EnablePartialRendering on the ScriptManager set to True.
4) I have AjaxControlToolkit.dll, Microsoft.Web.Extensions.dll, and Microsoft.Web.Preview.dll all in my bin directory.

Every update panel I've tried still does a standard post-back and whole-page refresh.

ANY ideas?

 

Well I presume that when you'r saying that you're using the latest, that you're using Ajax.net beta 2.

Have you try to start a Ajax.net web-site from vs?
Can you see the updatepanel in the vs toolbox?

I have been having the same issue.  It works on my PC in testing, but when I place the files on my IIS it does a normal postback and the whole page refreshes. I have the dll in my bin folder.  I placed my ScriptManager on my master page, EnablePartialRendering on the ScriptManager set to True.  I placed an update panel with a control on another page and used the triggers as described in documentation and set it to conditional.  Is there something I am missing? I am using Beta 2.0.  This worked in the old ATLAS version, but was getting validation conflicts now since I moved to the new version I can't seem to get it running properly.  Any suggestions would be appreciated.

I've since gotten basic UpdatePanel examples to work, proving that it's not a configuration problem on my part, but only when they're as trivial and useless as the examples on the Microsoft's website. Everything that I've tried with real-world complex code doesn't work consistently, if at all, without generating full-page post-backs.

One of the simplest examples I can site is a user control referenced within an update panel, and the user control is dynamicly adding asp:Button controls to the page. The click events of those controls always generate full-page post-backs from what I've seen. This is just one of several examples I've ran into.

I'm not trying to be a pessimist here. I really want Atlas to work, but I've had our own Ajax framework implmentation with asynch panels in our application for a year now and had less problems with it than with Atlas so far. I was really enthusiastic after all the hype, but the more I see of it, especially in the beta 2 stage now, the less impressed I am with it.

 

There are a couple of more advanced examples here:

http://ajax.asp.net/docs/tutorials/UsingUpdatePanelControls.aspx

I know it can be frustrating when you are expecting to see a non-flickering page (indicating a async postback) and then the whole page updates. The documentation can use some more information on using user controls with UpdatePanel controls.

Thanks for the reply and assistance.  However, I have it running on a local PC development environment, but can't seem to get it to work through the web when I place it on the web server IIS 6.0 x64 bit.  I used the config provided with some modifications for our connections, namespaces, etc.  I copied the dlls into the bin folder.      Is there something special I need to do with the server, dlls, config, or anything?

 

Thanks

I'm not too familiar with running it on x64 bit. If you copied the Microsoft.Web.Extensions.dll into your bin folder (you didn't install using msi) then you have to change the <compilation><assemblies> node of the Web.config to pick up the dll in the bin?

Fysh1, I have been running this on IIS6.0 x64bit and the UpdatePanel scenarios work fine. I would suggest that you download the http://www.fiddlertool.com/fiddler/ and monitor the requsts that are happening. Can you confirm that your app is working on one box and not on another - then we can try and ensure the settings on both boxes to whet out the problem. If you are running Beta2, it might be that the script resource handler is not registered on your production server and that is causing the ASP.Net AJAX javascripts to not be downloaded to your systems and ultimately causing full post-backs.

Hope that helps.

Thanks for the suggestion, I will post back once check into fiddler.  I have tested the program on several development pcs and it works with the installation of the AJAX beta 2.0.  However, I believe all we had to do was place the dlls in our bin folder and the program would know to search for them there.  Initially I installed the beta on the server and tested, but still didn't work.  CIO requested I remove the program from the server in fear of security holes.  I also remvoed them from the assembly in the config file sinec they were not actually in my assembly folder.  It was mention to have it redirected in the config file to the bin.  I am unsure of to go about doing this?  Can any light be shed on this?  Thanks and I will monitor and post back this weekend.

Wow I finally was able to get it to work.  It appears some of the info was missing from the config file.  Also, I used the msi to install on the server.  It works, but it looks like I will have to use the update progress portion since there is a slight delay when refreshing the listboxes that are related to other dropdown boxes.  Thanks for all the help.

 

 

What web.config items were missing?  I'm having the same issue and i've compared the web.config to several versions to make sure everything is in.

1. If you want to add the ASP.NET 2.0 AJAX Futures CTP, download and install it from the ASP.NET AJAX Downloads Web site.
If you want to add the ASP.NET AJAX Control Toolkit, download and install it from ASP.NET AJAX Control Toolkit Web site.

http://asp.net/AJAX/Documentation/Live/ConfiguringASPNETAJAX.aspx