MapBase/source-sdk-2013-mapbase
1
0
Fork 0
mirror of https://github.com/mapbase-source/source-sdk-2013.git synced 2025-03-03 17:25:27 +03:00
Code Issues Packages Projects Releases Wiki Activity

Integrate registry key fix for using VPC without Visual Studio 2013

Browse Source
This commit is contained in:
ALLEN-PC\acj30 2025-01-12 15:50:24 -06:00 committed by Blixibon
parent aab8755fcf
commit 0f6b4b4b8a
2 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
sp/src/vpc_scripts/newer_vs_toolsets.vpc
View File

@ -12,6 +12,10 @@ $Conditional VS2017 "0" // Toggles Visual Studio 2017 (v141) toolset
$Conditional VS2019 "0" // Toggles Visual Studio 2019 (v142) toolset
$Conditional VS2022 "0" // Toggles Visual Studio 2022 (v143) toolset
//
// WARNING: If you do not have Visual Studio 2013 installed and try to use VPC, it may produce an error about a missing RegKey.
// You can fix this without installing VS2013 by running newer_vs_toolsets_regkey_fix.reg, which is in the same directory as this file.
// This .reg file adds a registry key which is normally created by installing VS2013. You will only have to do this once per machine.
//
// VPC may still say "Generating for Visual Studio 2013" even when using one of the above toolsets. This message is irrelevant and can be ignored.
//

7
sp/src/vpc_scripts/newer_vs_toolsets_regkey_fix.reg Normal file
View File

@ -0,0 +1,7 @@
Windows Registry Editor Version 5.00
; https://github.com/ValveSoftware/source-sdk-2013/issues/72#issuecomment-326633328
; If you are running a 32-bit system, you may need to remove WOW6432Node from the path.
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\10.0\Projects\{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}]
"DefaultProjectExtension"="vcproj"