Last post Sep 18, 2012 12:09 PM by dezinnia
Sep 17, 2012 12:28 PM|dezinnia|LINK
Really simple web page... just implementing a single control (slideshow)...
Getting this error:
Parser Error Message: Could not load file or assembly 'AjaxControlToolkit' or one of its dependencies. The system cannot find the file specified.
And it's noting this line on my aspx page.
<%@ Register Assembly="AjaxControlToolkit" Namespace="AjaxControlToolkit" TagPrefix="ajaxToolkit" %>
My web.config file looks like this:
<compilation debug="false" targetFramework="4.0">
<add assembly="System.Design, Version=184.108.40.206, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.Web.Extensions.Design, Version=220.127.116.11, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add assembly="System.Windows.Forms, Version=18.104.22.168, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Web, Version=22.214.171.124, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
I've tried it on our regular host, as well as on godaddy, and I get the same error... (however, it displays fine when I run the local webserver via Visual Studio.)
Here's a page from the godaddy support site:
This is a note from that page:
"The ASP.NET AJAX assembly (System.Web.Extensions.dll) is installed in the global assembly cache (GAC). Do not include the assembly in the Bin folder of your AJAX-enabled website."
So I removed the dll from my bin folder, and I'm still getting the error. Removed the bin folder altogether, and I'm still getting the error.
Called godaddy, and they don't know what the issue is. (All they said was that it was a "fancy 404 error." Thanks.
Some posts talk about it being a mismatch between the version of AJAX in my app vs that on the server, but it would appear that godaddy has the current version.
Sep 17, 2012 04:41 PM|javedwahid|LINK
what about the AjaxControlToolkit.dll file, i'm pretty sure that you need that too
Sep 17, 2012 05:30 PM|dezinnia|LINK
Yes, I had that in there, and it wasn't working.
Then I saw the godaddy note about taking it out. (See above.)
UM, why are all the questions about AJAX Control Toolkit moved to the deployment section? I originally put this in the AJAX toolkit section because I thought someone there might have an idea.
Sep 17, 2012 05:33 PM|javedwahid|LINK
I didn't see anything on the GoDaddy page about the AjaxControlToolkit.ddl file
Sep 17, 2012 05:55 PM|dezinnia|LINK
ahhh... good catch.
But I did have the AjaxControlToolkit.dll file in there, and it still wasn't working.
Sep 17, 2012 05:59 PM|javedwahid|LINK
so put the ajaxcontroltoolkit.dll file in the bin folder, remove the system.web.extension.dll file from the folder and see what you get, is it the same error message? Are you sure you have the .net version set right?
Sep 17, 2012 06:09 PM|dezinnia|LINK
I don't believe there ever was a system.web.extension.dll file. (I guess that's why I was assuming they were talking about the ajaxcontroltoolkit.dll file.)
So, long story short, there shouldn't be any system.web.extension.dll file in the folder mucking anything up.
And it doesn't work.
Version should be 4.0. I've downloaded the most recent version of the toolkit (so I WOULD have the most current dll, if it was needed.)
And I'm specifying the current 4.0 assemblies in my web.config file.
It was built in Visual Web Developer 2010, and runs fine on my local web server that launches from VWD.
I've seen this error mentioned all over the web, but haven't seen anyone solving it. (They all do mention making sure the assemblies in the app and the server match, but I'm assuming they do, since Godaddy says they support. ATK 4.0)
Sep 17, 2012 06:14 PM|javedwahid|LINK
ok, so what about in your web.config, I don't see the ajaxcontroltoolkit listed in the assemblies section (not sure if it needs to be or not)
how are you deploying the website, are you using the publish feature in visual studio? and then uploading the published directory?
Sep 17, 2012 06:36 PM|dezinnia|LINK
I put the registration of the AjaxControlToolkit on that page, and that page alone. (No other pages in this particular project use it, so I wanted to make sure it was only on that page. (I think I have that syntax in my first post.)
I know I can put it in the web.config file instead, but I wanted to isolate the error to the one page. I built a second page that does a slide show without the toolkit, but I really want to solve this!
I'm deploying by simply copying the files to the webserver. It's a simple asp.net web site. Not a web application or anything.
Sep 17, 2012 06:40 PM|javedwahid|LINK
ok, I understand it's a website, but try publishing it, the code-behind files can still be compiled into the bin folder. not that it has any affect on this issue, but just a thought. So then all the other pages on the site, that are not using the toolkit
work? Try putting it in the web.config for testing purposes and see if it works or if that crashses the whole site.
Sep 17, 2012 10:09 PM|dezinnia|LINK
Can't publish. I'm using Visual Web Developer... I think it's the free version.
I guess I see one reason to buy a copy of Visual Studio, eh?
Sep 18, 2012 11:36 AM|javedwahid|LINK
yeah, but publishing is not really required though. but if you want to protect your code when you deploy, then yes. I can't think of any other reasons why you would still be getting the file not found error
Sep 18, 2012 12:09 PM|dezinnia|LINK
Ok, so, let's do a checklist (because I'm getting the error on godaddy as well as on our regular host)...
What am I missing?