J
John Kotuby
Hi all,
Just in case anyone gets this error and can't find the solution to their
problem by Googling it, here is what I discovered in my Web Project. I have
a rather large project that was started with VS2003 which I continually add
to and update. Very often if I need a new User Control that resembles an
existing one I will make a copy of it and then modify. Maybe that's a bad
practice...maybe not.
Anyway, I was getting "warning" errors in VS2008 (with the latest service
packs for it and .NET 3.5) that <asp:ScriptManager> is not a known element.
I searched the web and scoured my web.config. What I finally discovered was
that there were old references to System.Web.Extensions at the top of some
pages, like the one below.
<%@ Register Assembly="System.Web.Extensions, Version=1.0.61025.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35" Namespace="System.Web.UI"
TagPrefix="asp" %>
By removing those @Register entries from the page the warnings disappeared
and intellisense began showing me the ScriptManager as being available. Of
course I already had a reference to that Asssembly in my web.config, and
that is probably why my project compiled.
Just in case anyone gets this error and can't find the solution to their
problem by Googling it, here is what I discovered in my Web Project. I have
a rather large project that was started with VS2003 which I continually add
to and update. Very often if I need a new User Control that resembles an
existing one I will make a copy of it and then modify. Maybe that's a bad
practice...maybe not.
Anyway, I was getting "warning" errors in VS2008 (with the latest service
packs for it and .NET 3.5) that <asp:ScriptManager> is not a known element.
I searched the web and scoured my web.config. What I finally discovered was
that there were old references to System.Web.Extensions at the top of some
pages, like the one below.
<%@ Register Assembly="System.Web.Extensions, Version=1.0.61025.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35" Namespace="System.Web.UI"
TagPrefix="asp" %>
By removing those @Register entries from the page the warnings disappeared
and intellisense began showing me the ScriptManager as being available. Of
course I already had a reference to that Asssembly in my web.config, and
that is probably why my project compiled.