Thread overview
[Issue 20005] VC++ can exists in separate BuildTools folder (not only in Community\Enterprise)
June 25

KnightMare <> changed:

           What    |Removed                     |Added
            Summary|VC++ can exists in separate |VC++ can exists in separate
                   |BuildTools folder (not only |BuildTools folder (not only
                   |in Community                |in Community\Enterprise)

--- Comment #1 from KnightMare <> ---
VC++ compiler (if it needed to VD) can be installed by BuildTools installer
from MS.
and default folder is C:\Program Files (x86)\Microsoft Visual
Studio\20xx\BuildTools (not Comminuty or something)
so VD should use it too not only VSINSTALLDIRECTORY

2nd (dunno how done for now, maybe next already is done):
such folder can contains many SDKs with diff versions:
C:\Program Files (x86)\Microsoft Visual
C:\Program Files (x86)\Microsoft Visual
each of such folder contains own include, tools and libs. last two with diff
host and guest archs - bin\Hostx64\x64 or lib\arm.

every update of VS and BuildTools can delete old and add new SDK.

so VD should contains option to select with SDK should be used or just "update to newest SDK" where VD will select lastest SDK from both folders (if they are exists) by number of SDK - 14.21.27702 is latest one.

June 25

--- Comment #2 from KnightMare <> ---
to 2nd:
when VD refs to some concrete SDK and on some running of VS (check at startup)
can see that this SDK does not exists then VD can select latest SDK

August 04

Rainer Schuetze <> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
                 CC|                            |
         Resolution|---                         |FIXED

--- Comment #3 from Rainer Schuetze <> ---
Buildtools now also supported by

regarding SDK version: Visual D detects SDK versions on every start similar to the VS batch vcvarsall.bat and sets environment variables accordingly and uses these for the respective settings. This makes it agnostic to updates of the Win10 SDK, but might not work when switching to older SDKs.