Visual Studio Distributed Side by Side / Error DependentAssembly

Question

(I am running Windows7 and using Visual Studio 2010.)

I use ClamAV in a .NET Azure project, and I run side errors whenever I run clamd.exe either through my code or by running clamd.exe on it.

In Visual Studio 2010, I get the error message:

Win32Exception was not processed. The application could not be started because its side-by-side configuration is incorrect. See application event log or use sxstrace.exe command line tool for more details.

And in Event Viewer I get:

Failed to create activation script for "C: \ Users \ pconerly \ code \ AntiVirus_source \ WorkerRole \ ClamAV \ clamd.exe". Dependent assembly Microsoft.VC80.CRT, processorArchitecture = "x86", PublicKeyToken = "1fc8b3b9a1e18e3b", type = "win32", version = "8.0.50727.6195" cannot be found. For detailed diagnostics, use sxstrace.exe.

When I searched for "8.0.50727.6195", it led me to rename 2005, so I downloaded it http://www.microsoft.com/download/en/details.aspx?id=3387

After rebooting, I still get a side-by-side error. Also, I think the redist installer is not completing its installation - as if it sees visual studio 2010 and says "oh, that's good enough, I don't need to install." I did not try to uninstall 2010 and use 2005 because the rest of my Dev team uses VS 2010.

What a deal? How can this be fixed? I am ready to pull my hair out.

Answer 1

You mentioned the version you mentioned here

Microsoft Visual Studio 2005 Service Pack 1 (MFC) Security Update

Answer 2

Link Timores is an update for Visual Studio. The actual distribution package is as follows:

http://www.microsoft.com/en-us/download/details.aspx?id=26347

Answer 3

Timos is right: the redist must be this one , which is associated with this KB entry. As you can see there, msvcr80.dll has been updated to version 8.0.50727.6195. This is a "security update" for "SP1" for the 2005 C ++ runtime. Your exe probably requires (through an internal manifest) this particular version.

If it is not found in the system (there are a lot of places to find) or in the current folder (with a suitable manifest aside), it will not load exe, since it cannot "activate the context", that is, load the specific DLL needed in the manifest.

I had similar problems when my system was updated (Windows updates), and recently compiled EXE files did not work with the old version installed in the same folder. I had to update msvcr80.dll and its manifest (which I found deep in \ windows \ winsxs) for everything to work.

Context activation is a tricky question anyway :)

Hth