Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't polute system folders with .dll files #34

Open
Tobbe opened this issue Apr 17, 2009 · 3 comments
Open

Don't polute system folders with .dll files #34

Tobbe opened this issue Apr 17, 2009 · 3 comments

Comments

@Tobbe
Copy link
Owner

Tobbe commented Apr 17, 2009

Copy the msvcp???.dll files to $litestepdir$ instead of system32 (check system32 if they already exists first)

@the-golem
Copy link
Contributor

If they already exist, wouldn't they be in system32 in the first pace? And if that's where they would have existed in the first place, how is it "polluting" the system folders by putting them where they're supposed to go?

@Tobbe
Copy link
Owner Author

Tobbe commented Nov 21, 2011

From this MSDN link: http://support.microsoft.com/kb/326922 :

For Msvcr70.dll or for Msvcr71.dll, you should install the CRT DLL into your application program files directory.
You should not install these files into the Windows system directories.
For Msvcr80.dll and for Msvcr90.dll, you should install the CRT as Windows side-by-side assemblies.

More discussion here: http://superuser.com/questions/228265/why-not-install-msvcr71-dll-into-system32

@the-golem
Copy link
Contributor

Well, a simple search of "msvc" turns up dozens of duplicates of files on my computer. Seems like many applications are doing as the MSDN link suggest. However, if possible, I think the msvc*.dll files should be shelved maybe into their own folder instead of just flatly within LitestepDir

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants