3

I have a complex app which cannot be linked statically with the CRT, but on the other hand does not require admin privileges to be installed (since it isn't doing anything that requires it). The normal way for installing the CRT so it can be linked to dynamically is to install the MS distributable CRT, but it requires admin privileges.

I am contemplating simply placing the MSVCRT100 DLLs in the same directory as the executable in order to alleviate the problem, but I'm not sure whether this practice has any downsides since it's not condoned or condemned anywhere I seen. Is there any reason not to do it, other than following the usual practice of static linking vs. installing the distributables?

Eldad Mor
  • 5,405
  • 3
  • 34
  • 46

1 Answers1

5

The short answer is yes you can.

It's even one of the option descibe on microsoft website to deploy application http://msdn.microsoft.com/en-us/library/dd293565.aspx

Copy the appropriate MFC and C Run-Time (CRT) library files—for example, for an x86 platform and Unicode support, copy mfc100u.dll and msvcr100.dll from \Program Files\Microsoft Visual Studio 10.0\VC\redist\x86\—and then paste them in the \Release\ folder of your MFC project. For more information about other files that you might have to copy, see Determining Which DLLs to Redistribute.


The downside is that the redistributable package is updated by microsoft security fixes. So if a security fix is deployed your application would not use it and may remains unsafe. I'm not a big fan, but it's the idea of the winsxs directory, and manifest since visual 7.0 which 'helps' your application to always use the best version.

ColdCat
  • 1,192
  • 17
  • 29
  • We ship the MFC DLLs with our product and install them into our bin folder. This allows an easy "copy install". – xMRi Nov 06 '13 at 11:00
  • "when you deploy app-local, even though you have a local copy of the DLL, when your DLL is loaded, if there exists a policy in WinSxS to redirect requests for the version of the DLL you are trying to load to a centralized version, your app will load the updated version. This is the main benefit VC derives from using fusionized (WinSxS) DLLs." [source](http://blogs.msdn.com/b/vcblog/archive/2007/10/12/how-to-redistribute-the-visual-c-libraries-with-your-application.aspx) – bouvierr Jun 21 '15 at 15:39