468,119 Members | 1,820 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,119 developers. It's quick & easy.

HELP! Ajax has died

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.

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.

Dec 7 '07 #1
2 1180
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;

"Arthur Dent" <hi*********************@yahoo.comwrote in message
news:E9**********************************@microsof t.com...
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.

Dec 10 '07 #2
Med
As far as I know, I think you can have two different versions of a dll file
referenced to your project, however you have to remove duplicate references
in your web.config this is what I did:

NOTE: FIRST BACKUP YOUR CURRENT WEB.CONFIG FILE BEFORE MAKING ANY CHANGES.

Example: I had reference to both versions in my web.config, so I searched
and removed the the entire line containing the old verion. In ths case
Version=1.0.0.0
<add assembly="System.Web.Extensions.Design, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>

<add assembly="System.Web.Extensions.Design, Version=3.5.0.0,
Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>

Hope this helps

Regards
Med

"Arthur Dent" <hi*********************@yahoo.comwrote in message
news:2A**********************************@microsof t.com...
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;

"Arthur Dent" <hi*********************@yahoo.comwrote in message
news:E9**********************************@microsof t.com...
>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.


Dec 11 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

6 posts views Thread by wukexin | last post: by
3 posts views Thread by Colin J. Williams | last post: by
7 posts views Thread by Corepaul | last post: by
13 posts views Thread by didacticone | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.