DLL Loading errors after installing Service Pack 1 of Visual Studio.

  • Thread starter Thread starter cpasmwalolo
  • Start date Start date
C

cpasmwalolo

Hello thezre,

I recently installed the SP1 of visual studio, just before releasing a new
version of my application. And I never though that this SP1 could change
something fondamental in the final executables and DLLS, but it happened.
All my C++ Dlls can not be loaded anymore on other machines that my current
development machine.

I read that I have to upgrade the VC++ DLLs, but what is exactly the DLLS
that I need to upgrade on the user machine ? Is there somewhere a list of
DLLs to upgrade, a setup . (not a msm, i do not use a packager that can
handle it).

Thank you

Laurent
 
I recently installed the SP1 of visual studio, just before releasing a new
version of my application. And I never though that this SP1 could change
something fondamental in the final executables and DLLS, but it happened.
All my C++ Dlls can not be loaded anymore on other machines that my current
development machine.

I read that I have to upgrade the VC++ DLLs, but what is exactly the DLLS
that I need to upgrade on the user machine ? Is there somewhere a list of
DLLs to upgrade, a setup . (not a msm, i do not use a packager that can
handle it).
Click to expand...

The DLLs that you should redistribute are contained in vcredist.exe
See
http://blogs.msdn.com/nikolad/archi...-of-vcredist-exe-shipped-with-vs2005-rtm.aspx
 
Yes I found it , I expected to find that in the Redist directory of the VC
directory. Anyway let's have a try.

Thanks

Laurent
 
Hi Bruno,

I think I have also run into this problem with the ExcelDna library.
After installing the service pack and recompiling, my .dll library no
longer loads on some PCs.

My C++/CLR application is just a .dll library, and used to work on a
PC with a vanilla .Net 2.0 installation. When compiling my library
with Visual Studio 2005 Service Pack 1 it seem no longer to work on a
vanilla .Net 2.0 installation. I would like to compile my library to
load using the released VC runtime, as it did before. Adding an
installer (that would require adminstrative access to install
VCRedist) is not appropriate for my case.

Is there any documentation for this breaking change, or a workaround I
can use when compiling? Should I uninstall Visual Studio Service 2005
Pack 1, or is there some manifest file I can edit so that my library
can work again?

Thanks for any help.

Govert
 
Back
Top