How can I change the path of visual studio that Burst is looking for? My installation is not on C drive.
It’s actually annoying that it complaints only when I build a client and not when I run it in the editor (but I understand it’s due to the fact that the AOT generated code is linked using the vs build tools)
I just want to let you know that after I gave up trying to understand how to let Burst use a different installation folder, I spent one hour to try to make it work again. Eventually I didn’t solve it, but I ended up with uninstalling all the versions of visual studio and unity, plus build tools and windows SDK before I ran out of time and I had to leave the office. I expect better.
This is what I got after uninstalling everything and installing 2019.2.17 with the VS studio it ships with. Usually this procedure fixes the problem. not this time:
BuildFailedException: Burst compiler (1.2.0-preview.12) failed running
stdout:
Burst requires Visual Studio (installable via Add Component in the Unity Installer) & the C++ build tools for Visual Studio, along with the Windows 10 SDK in order to build a standalone player for Windows with X64_SSE4
Unable to find a valid windows 10 SDK at ‘C:\Program Files (x86)\Windows Kits\10\Lib\10.0.18362.0’
Turns out windows 10 SDK is not optional and it must be installed along Visual studio OR Build Tools, WITHOUT changing the default installation folder. It also seems that a specific windows SDK 10 version must be installed. I will try the process again even if the first time it miserably failed.
Edit: installing that specific version of windows 10 SDK made it work. I will not try to uninstall visual studio and install visual studio build tools because : a) I wasted too much time on this b) I am pretty sure I did it the first time and broke everything again.
First off - sorry you are having these platform issues with Burst / Visual Studio.
Burst 1.2.0’s MSVC detection uses the vswhere program to detect where Visual Studio is - I’m not very well versed in how it does this but I think its using registry keys. We also use registry keys to detect the Windows 10 SDK location too.
Hello thanks, surely there is something wrong, but yesterday I have been told that you are working to remove all the dependencies to external version of VS. That’s all I want at this point 
We are indeed - it won’t be until Burst 1.3.0.preview.1 (no exact ETA on when that is going to be released, but soon-ish after 1.2.0 final is cut), but it should allievate your problems!
Thanks Using VS Preview 2019 (and dont wont install both vs) on standart C drive, and also have the bug, try latest preview 1.3.0 preview 10 its working with VS Preview