R
Rudolf Meier
Guest
Why is it different again???
2015 and earlier... well, we don't have to talk about this.
2017 -> ..\Common7\IDE\VC\VCTargets\BuildCustomizations
2019 -> ..\MSBuild\Microsoft\VC\v150\BuildCustomizations and ..\MSBuild\Microsoft\VC\v160\BuildCustomizations
... I need to build a setup to install such customizations. Now... how can I find those paths at runtime and why do we have 2 directories in 2019? And why is it changing with EVERY Visual Studio version?
Or... can we finally (in 2017 this doesn't work... yes, I have tried it) install BuildCustomizations via the Extensions directory? (no, I haven't tried it for 2019)
Rudolf
Continue reading...
2015 and earlier... well, we don't have to talk about this.
2017 -> ..\Common7\IDE\VC\VCTargets\BuildCustomizations
2019 -> ..\MSBuild\Microsoft\VC\v150\BuildCustomizations and ..\MSBuild\Microsoft\VC\v160\BuildCustomizations
... I need to build a setup to install such customizations. Now... how can I find those paths at runtime and why do we have 2 directories in 2019? And why is it changing with EVERY Visual Studio version?
Or... can we finally (in 2017 this doesn't work... yes, I have tried it) install BuildCustomizations via the Extensions directory? (no, I haven't tried it for 2019)
Rudolf
Continue reading...