![]() ![]() Licensing Restrictionsįaculty and staff can install this software freely, as long as they can login with an Administrator-equivalent account. The Visual C++ redistributable packages can be distributed with any application compiled with the corresponding version of Visual Studio. Freely distributable, and can be downloaded from.Microsoft Visual C++ 2005 or 2008 or 2010 Redistributable, for 32-bit (x86) or 64-bit (圆4) applications.If (Regex.IsMatch(value, 2015.*\(x86\)")) //here u can specify your version.Ĭ++ 2017 is valid replacement for C++ 2015 so if you want to check it as well edit the regex like this: Regex.IsMatch(value, (2015|2017). ![]() If (string.IsNullOrEmpty(value)) continue Var value = subDir.GetValue("DisplayName")?.ToString() ? null Using (RegistryKey subDir = (dependenciesPath + "\\" + subKeyName)) String dependenciesPath = (RegistryKey dependencies = (dependenciesPath))įoreach (string subKeyName in dependencies.GetSubKeyNames().Where(n => !n.ToLower().Contains("dotnet") & !n.ToLower().Contains("microsoft"))) It is hard to get all registry values for VC 2015 so I have written a small function which will go through all dependencies and match on specified version(C++ 2015 x86) public static bool IsVC2015x86Installed() I only know one kind of programmer that does not do that: The one never tested his program on a freshly installed Windows (Virtual Machines work) and thus is not aware the requirements even exists (because every other program installs VC Redist and current DX versions). ![]() But that is just "making certain it is there" from a slightly different angle. The only slight modification I know off is Steam, which runs those installers under Elevated rights before a program is executed for the first time. It is the administrators job.Įvery installer does that, not the least of which are the Visual Studio and SQL Server ones. If that somehow did not work, there is nothing your puny usercode can do to fix it at runtime. If it was damaged, hopefully the installer will fix the installation. If it was not there, it will now run under Administrator rights and be there afterwards. If it was already there, the Installer will just do nothing. Let it be executed as part of the normal "Elevated Rights required" Installation process. The basic answer is: Do not bother if it is there at runtime. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |