asp controls unknown inside updatepanel in nested master

I have a master page with scriptmanager and update panel outside the contentplaceholder. Immediately the updatepanel and all nested master and non-master pages show all asp elements as unknown. If I move the update panel to inside the nested master content element it is still unknown as is all of the nested elements and pages.

I am running the december releases. I have un-installed and re-installed a couple of times. This is always the behavior. The code runs, but there is not intellisense and virtually everything is marked with the red underlines, and the error page is full (but doesn't stop the app coming up).

I looked at a number of posts suggesting rebuilding the toolbox. Nothing seems to help. However, the ajax toolkit controls are recognized because there is an @dotnet.itags.org.Register in the nested master.

Additionally, despite the post I found saying it had been fixed, I must keep my master pages open or none of the controls on any of the lower pages are recognized.

Anyone know of a post I missed about this issue?

/bump

I have the same issue.

In visual studio i create a new Ajax enabled website. I create a master page and a content page. The content page is to contain an update panel with some stuff in it. The AjaxControlToolkit is recognized while the Update Panel is not.

Cheers,

Michael

I'm also having this same problem. I have a Master page and my update panel is in the content page. AjaxControlToolkit controls are recognized but any controls within the update panel are not.
I'm also having this same problem. I have a Master page and my update panel is in the content page. AjaxControlToolkit controls are recognized but any controls within the update panel are not.

bump

I have 2 update panels (master/detail) that I am wiring together.

I am trying to make an object data source in UP2 use a praramater from a gridview in UP1. On creation of the data source, the Master gridview is not visible, but I hard coded it, and it actually works fine.

I think this is a bug in the UI of VS 2005.

Make sure you have the content inside your update panel wrapped with <ContentTemplate></ContentTemplate>