Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / General / December 2007

Tip: Looking for answers? Try searching our database.

Can't access System.Web.Extensions

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Arthur Dent - 09 Dec 2007 21:59 GMT
Hello all, I have a site which was a .NET 2.0 AJAX 1.0 site.

I opened it up in VWDExpress 2008, and changed it to a 3.5 site, then
subsequently changed it back to a 2.0 site (I didn't have time to figure out
the subsequent C# compilers error in the web.config - which is strange BTW,
since this is a VB site, not C#).

Now, my references to AJAX no longer work. The web server has both the new
(3.5), And old versions (1.0.61025.0) installed.
If I look at the references in my project properties, it shows
System.Web.Extensions, 1.0.61025.0 as an included reference, from the GAC.

However, if I look in the object browser, filtered to "My Solution", it does
not show the System.Web.Extensions library or namespace.
and my pages are all throwing parser errors...
   Unknown server tag 'asp:scriptmanagerproxy'.
   Line 13:     <asp:scriptmanagerproxy id="ScriptManagerProxy1"
runat="server" />

I have tried removing and readding the reference but that didn't help.
I have tried adding the System.Web.Extensions to the global namespace import
section in the web.config, but that did not help.

I don't know what else to do to try to fix this, short of redoing the
website, which is a LAST resort, as it's rather large.
Arthur Dent - 10 Dec 2007 17:54 GMT
Okay --- for posterity's sake...

I found the problem; When I the switch between 2.0 > 3.5 > 2.0 futzed up the
reference to System.Web.Extensions... in the process it also 'undid' all the
manual web.config changes necessary to a 2.0 app to use AJAX.

So here is what I did...

first, I manually removed the ScriptManagerProxy from a page, then loaded it
in design view, and manually readded a new ScriptManagerProxy.

then I had to go back, and put all the web.config alterations back in.

HTH someone in the future;

> Hello all, I have a site which was a .NET 2.0 AJAX 1.0 site.
>
[quoted text clipped - 25 lines]
> I don't know what else to do to try to fix this, short of redoing the
> website, which is a LAST resort, as it's rather large.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.