I downloaded the latest release today, and dropped it in as a replacement for the older version of my project. When I deployed this on our production webserver, I got errors about not being able to find vswebsite.interop. I don't know what this is, but from a couple of quick searches, I would guess that it's something to do with providing designer support in Visual Studio. My question is why has this been added as a dependancy of the control toolkit, and if it is intentional, how would I go about installing this on a production webserver without installing visual studio?
From what I can see this is something to do with web project support in visual studio.
Richard
I'm having the same issue. I've tried uploading the bare bones version of an AJAXEnabledWebSite to a hosting account and I've also tried uploading to a server. Both of which gave me the same error. However when loading any other VS built website those ran fine... Please if you get anywhere with that error let me konw.
-CJ
Description:An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message:Could not load file or assembly 'VsWebSite.Interop, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
Source Error:
Line 32: <add assembly="System.Web.Extensions.Design, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>Line 33: <add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>Line 34: <add assembly="VsWebSite.Interop, Version=8.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/></assemblies>Line 35: </compilation>Line 36: <httpHandlers>
Source File:D:\Inetpub\wwwroot\ajaxenabledwebsite1\web.config Line:34
Assembly Load Trace: The following information can be helpful to determine why the assembly 'VsWebSite.Interop, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' could not be loaded.
WRN: Assembly binding logging is turned OFF.To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.Note: There is some performance penalty associated with assembly bind failure logging.To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210
FWIW, I found that you can just remove that line from the web.config when deploying to a production server and everything seems to be ok. Not sure why it was put in in the first place, because whether it is there or not doesn't seem to make a difference.
When I take that line of code out of the web.config file and upload this is the new error i get: any other ideas?
-CJ
Description:An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details:System.IO.FileNotFoundException: Could not load file or assembly 'VsWebSite.Interop, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.Assembly Load Trace: The following information can be helpful to determine why the assembly 'VsWebSite.Interop, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' could not be loaded.
WRN: Assembly binding logging is turned OFF.To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.Note: There is some performance penalty associated with assembly bind failure logging.To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
When I take that line of code out of the web.config file and upload this is the new error i get: any other ideas?
-CJ
Description:An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details:System.IO.FileNotFoundException: Could not load file or assembly 'VsWebSite.Interop, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.Assembly Load Trace: The following information can be helpful to determine why the assembly 'VsWebSite.Interop, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' could not be loaded.
WRN: Assembly binding logging is turned OFF.To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.Note: There is some performance penalty associated with assembly bind failure logging.To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
If I remove the line AFTER I deploy to production then it works fine. The problem is, every time I publish the site it puts it back in, so you can't just remove it from your web.config and expect it to work... This is definitely an issue that needs addressing...
I get the error, too. It's a major issue and needs to be addressed ASAP.
okay so what i did that seemed to solve the issue was I found VsWebSite.Interop.dll on my machine and uploaded that into the bin folder. then I leave that line of code and it runs. what a pain tho.
Good workaound though not a good solution. We're working on this, stay tuned.
It's probably Visual Studio that's adding that line (typically whenever you do a build). The 10606 Toolkit has an new dependency on VsWebSite.Interop.dll, but that file's needed *only during development* (it's for interacting with the designer, I believe). So it's fine to go to production without that line in web.config, but I can see how it'd be annoying to have it added all the time. I've pinged Ted/Shawn since they're more familiar with the details of this than I.
I had the same problem...
I solved this doing:
1.- Open .\AjaxControlToolkit\AjaxControlToolkit.csproj
2.- Expand the References,Click on "VsWebSite.Interop" and set "Local Copy?" [Sorry, But I'm Using the Spanish VS version :$] to TRUE.
3.-Make the DLLs
(Now In my Bin\Release folder I have 2 Dlls. AjaxControlToolkit.dll and vswebsite.interop.dll [and the "cultures folders" if was in "Release"] )
After that, I Added the reference to the new AjaxControlToolkit.dll, and the Web Works fine..
EDIT: In a 2nd test, I'd need copy the vswebsite.interop.dll to the bin folder...
After this 2nd test, I saw that Before do that Steps, If I remove that line before compile the web, The line appears again after Compiled ... Now, This don't occur)
____________________________
-- Sorry For My English Mistakes... :( --
I'm having this issue as well, except removing the line from the web.config file on my server does not seem to work. I get the generic "Runtime Error" message after doing that, informing me to turn CustomErrors mode to Off, although it is already off in my web.config file. Where is the vswebsite.interop.dll file located?
This assembly isn't needed at runtime - the problem you're probably seeing is that the deploy step is sticking the reference back into the web.config.
We're working on a fix for this. In the meantime, make sure the web.config that's on the server doesn't have this reference.
its in some odd place in the VS 2005 folder in program files... just do a search for it.
According tohttp://www.codeplex.com/AtlasControlToolkit/WorkItem/View.aspx?WorkItemId=10994, this issue has been closed as part of release 10615. But, I don't understand the whole codeplex thing and what this really means.
No comments:
Post a Comment