Wednesday, January 17, 2007
Microsoft AJAX ATLAS intellisense for html doesn’t work
The other day I was having a problem while building aspx pages in Visual Studio using Microsoft AJAX control toolkit where even though I had setup the web.config file properly and the page worked in the browser, when I was in the editor, I would get red squiggly marks indicating that the tags I was using were invalid whenever I used an Microsoft AJAX ATLAS component.
The problem for me was that every page that uses any MS AJAX features must have a ScriptManager control on the page. So in order to avoid having to put a ScriptManager manually on each page, I declared it once on the master page. This allows the page with the MS AJAX control on it to render the control using the ScriptManager from the master page.
But in the Visual Studio editor, when I would close the Master page file, suddenly every page with an AJAX control would break. At first their working and not working seemed completely random because I didn’t realize that it had anything to do with the master page but then I realized that for some reason when the file was closed, it was no longer in memory and as such, the aspx page that I was working on that relied on the master page didn’t know that the master page had the declaration on it for the ScriptManager. That’s my theory on why it breaks at least.
So the solution for now is to just keep the Master page open while you’re working on pages that rely on it that have AJAX controls on them. Microsoft is supposed to be releasing a patch soon to fix this though in SP1. ¶ 8:27 PM
The other day I was having a problem while building aspx pages in Visual Studio using Microsoft AJAX control toolkit where even though I had setup the web.config file properly and the page worked in the browser, when I was in the editor, I would get red squiggly marks indicating that the tags I was using were invalid whenever I used an Microsoft AJAX ATLAS component.
The problem for me was that every page that uses any MS AJAX features must have a ScriptManager control on the page. So in order to avoid having to put a ScriptManager manually on each page, I declared it once on the master page. This allows the page with the MS AJAX control on it to render the control using the ScriptManager from the master page.
But in the Visual Studio editor, when I would close the Master page file, suddenly every page with an AJAX control would break. At first their working and not working seemed completely random because I didn’t realize that it had anything to do with the master page but then I realized that for some reason when the file was closed, it was no longer in memory and as such, the aspx page that I was working on that relied on the master page didn’t know that the master page had the declaration on it for the ScriptManager. That’s my theory on why it breaks at least.
So the solution for now is to just keep the Master page open while you’re working on pages that rely on it that have AJAX controls on them. Microsoft is supposed to be releasing a patch soon to fix this though in SP1. ¶ 8:27 PM
