Hi,

I've created my website and now want to deploy it.  How do I get it to take along the necessary DLL's?

Tx,

Herman

Yes, I have full control of the server.  I added the DLL's to the GAC, but still ran into some problems... Web.config contains reference to several assemblies that are not available on the webserver (a W2K3), removing them from web.config does not impede the website.  But VS2005 re-adds them everytime we rebuild the site.  The only reference I googled was that these are somehow connected to EnvDTE, not including the reference to a license-dll that I cannot find on my system.

<add assembly="VSLangProj2, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>

<add assembly="VSLangProj, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>

<add assembly="VSLangProj80, Version=8.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>

<add assembly="MicroFour StrataFrame License, Version=1.3.0.0, Culture=neutral, PublicKeyToken=4A99020E74365197"/>

Any help would be appreciated.

Herman

I'm not sure why it's adding those references back into your web.config file... none of our websites automatically add in dependencies if the reference isn't manually there. I suspect that it has to do with some option within Visual Studio that is automatically adding in the references, but I cannot find it. The root of the problem is that our Extensibility DLL is referenced by our other DLLs, and it in turn references the DLLs that are being pulled into your web.config file. An up coming version will remove the reference to Extensibility from all of our DLLs, but we must undergo adequate testing to ensure that all of the type editors work as they should before releasing it.