RTM: Could not load file or assembly System.Web.Extensions or one of its dependencies

Geeks only.

Perhaps if you weren't quite as exaggeratory or sarcastic it would be easier to receive help. That being said.
I haven't had any issues rolling to RTM. I have been using MS Ajax since it was Atlas December 2005 CTP. I installed the RTM after uninstalling Beta 2 and I haven't had any problems on my machine (loca) or on the server. I don't host, I have my own server so perhaps your situation is different. Are you having issues on the server as well as your local environment?

http://weblogs.asp.net/scottgu/archive/2007/01/25/links-to-asp-net-ajax-1-0-resources-and-answers-to-some-common-questions.aspx

Most web hosting companies that are good in nature will implement the RTM release. If not you should contact your hosting company and find out if they will support the MS Ajax RTM.

Most of the time I find that the issue is PEBKAC (Problem Exists Between Keyboard And Chair)

JoeWeb

I'm sorry if I sounded sarcastic, but I was really under the impression that this was maybe not entirely ready to fly. My fear is that if I can't get it to work quickly, my clients will never get there. So when I struggle through various (un)installs and feel I really followed all the directions, I'm obivously overlooking something and so will they. As it turned out it was in the web.config (I installed the toolkit and saw that it ran without the dll in the bin directory so I knew it had to work somehow):

add

assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"instead of

add

assembly="System.Web.Extensions"Somehow I got the second in the web.config until I noticed the discrepancy. This now proves to me that Ajax will function in a shared hosting environment, which is what I needed to have proof of.

Thanks for your time,

Peter

I don't think you sounded sarcastic at all. There are challenges we all face and it's better to share and learn than to sit in quiet and pull your hair out.

I've been using this for a while and on publish and moving docs to the remote host I get this error

Parser Error Message:Could not load file or assembly 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The

[No relevant source lines]

I'm not using the GAC as it isn't accessible to me so I have to use the Bin folder.

This kind of thing happens a lot I've come to find. Follow the exact same steps each time doesn't necessarily create the same results.

This vauge error [No relevant source lines] is a bummer and it's not always the same problem. What has anyone else found?

JonF:

Parser Error Message:Could not load file or assembly 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The

[No relevant source lines]

You get this error, if you don;t have it installed in the GAC, because it is looking for the assembly in the GAC. Just remove the ", Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" from the string (in ALL placed you see that in the web.config) and it should solve the issue.

-Alan

I found one other thing to try.

<!--
Comment out this line and put the DLL's in the Bin for the appropriate app.
I'm not sure what sort of security implications this may have however.
-->
<trust level="Medium"/>

I meant to add that this line of code is in the Web.Config.

I don't see a way to edit your posts here once you've posted them.. <shurg></shrug>

I meant to add that this line of code is in the Web.Config.

I don't see a way to edit your posts here once you've posted them.. <shurg />

Okay, I have the exact error. I found that in the .aspx page in the RegisterVersion=2.0.0.0 instead of versionVersion=1.0.61025.0 then I'll get that same error. How do I resolve this problem because if I drop the script manager into the page, it automatically put in version 2?

Just stating the obvious here.

Have you all ensured that you have your web site configured to run as an asp.net 2.0 web site instead of 1.1?

I uninstall MS .Net Framework 3.5 (Pre-release version) and it all worked fine.