On some of my pages, I get an error using <asp:UpdatePanel...>

The page works when run, just that the IDE shows an error. This wouldn't be a problem except that I have elemenets inside the update panel that are not exposed in the codebehind...

I have read some about this, and I have seen some solutions, such as opening your master page, etc... I have done all this. Just not sure what to do.. this is starting become quite troublesom!

Any ideas? 

I find that the errors usually occur when there is another error somewhere in the application (not always true but a possibility).  As far as seeing your variables in the code behind, I usually can get them to show up if you save anychanges on the aspx page and then do a build page you will usually see them in code behind at that point.  If it becomes to much of an issue one solution I find works ok is to make a single Test page in your project and don't tie it to a master page and when you need to see intellisense your not normally getting just copy everything into the test page and try it.  Not the most elegant but it seems to work.

 If you find a better solution let me know.

AjaxButter

well, I ended up closing the master page and reopening it... which worked, and then about an hour later, it was happening again.

I have heard that this is an issue, but I am not sure why? And is Microsoft planning on addressing the issue? 

Yeah that sometimes works also.  Im guessing its an issue just because ajax works in a manner that visual studio was not initially designed for but I could be wrong about that.  I would guess that it would be something they would plan on fixing but at a very low priority level.  Maybe someone on the Ajax team or Visual studio developer can shed some light on if this will be corrected.

AjaxButter

Did you delete old Atlas binaries from bin after installing final Ajax release? You may also have to fix web.config if you used older version of Ajax.

http://ajax.asp.net/documentation/Migration_Guide_CTP_to_RTM.aspx

http://ajax.asp.net/documentation/Migration_Guide_RC_to_RTM.aspx

http://ajax.asp.net/documentation/AspNet_AJAX_CTP_to_RTM_Whitepaper.aspx

This has nothing to do with Visual Studio. Atlas Ajax is a set of updated controls which VS is able to handle without any changes. The issue is that when you upgraded to Ajax RTM new assemblies are installed in GAC. When you also have older assemblies in bin intellisense engine is getting confused which ones to use as they contain same types.

I am running the latest version of ajax and toolkit and still experience that every now and then but like I said its sparatic. There are no old dll's in the bin and I have removed without problems all old version of ajax.  As far as the web.config I have been very vigilant about keeping it up to date as soon as i install a newer version i update the config using white papers that were released with that version.  Not sure if there is any temporary files that may have gotten created that didnt get deleted after an update that possibly cause the issue with intellisense engine?  As I said it almost seems to surface when you introduce another error on the page but that is not always the case. 

AjaxButter

I also have this problem, specifically when using Master Pages with Update Panel.  scriptmanager control is in the master page, as it should be, but adding an updatepanel to the web page itself causes the "element is not a known element" error.

This is a clean install of VS2005 and neither CTP or RC were previously installed.

I've seen various references to this problem elsewhere, but can't seem to locate a definitive solution.  If this is a widespread issue I can't see how the AJAX components are useable.

Derek

This is with SP1 in my case

Not sure if you meant Service Pack 1 for visual studio.  Don't think there is a SP 2 for visual studio yet unless its in very early stages of beta.  You are correct though the issue appears on content pages that have a master page set.  The error list usually will fix itself within 5 mins or so of being on the page.

 AjaxButter

I've just installed SP1 and this seems to fix the problem in any new Ajax enabled web sites but not in and older sites to which Ajax components are added. 

So do I need to add specific web.config settings to the older site to make this work?

Derek

Yes. You can fing migrations guides here:

http://ajax.asp.net/documentation/Migration_Guide_CTP_to_RTM.aspx

http://ajax.asp.net/documentation/Migration_Guide_RC_to_RTM.aspx

http://ajax.asp.net/documentation/AspNet_AJAX_CTP_to_RTM_Whitepaper.aspx