Monday, May 8, 2017

Can't force MSBuild to use a different SDK Tools path

My scenario is: my build server, which uses Jenkins as the CI tool, runs on Windows 2008, which does not support the newer Windows 10 SDK. So I tried playing with both SDKToolsPath and FrameworkOverride msbuild command line parameters, but without success (although not the two together). I ended up trying a hack I thought of while the question from this thread (the link points to this very solution I posted there) - overwriting the lc.exe from SDK 7 with the newer LC.EXE from SDK 10. My build finally succeeded. Did not spot any side effects so far...

No comments:

Post a Comment