https://issues.dlang.org/show_bug.cgi?id=19624

Rainer Schuetze <r.sagitario@gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |r.sagitario@gmx.de

--- Comment #1 from Rainer Schuetze <r.sagitario@gmx.de> ---
I suspect your installation without any workload caused the default paths to be wrong. Here are the usual settings for DMD/x64:

Executable paths:
$(VCTOOLSINSTALLDIR)bin\HostX86\x86
$(VSINSTALLDIR)Common7\IDE
$(WindowsSdkDir)bin
$(DMDInstallDir)windows\bin

Library paths:
$(VCTOOLSINSTALLDIR)lib\x64
$(UCRTSdkDir)Lib\$(UCRTVersion)\ucrt\x64
$(WindowsSdkDir)lib\$(WindowsSdkVersion)\um\x64

Linker:
$(VCTOOLSINSTALLDIR)bin\HostX86\x86\link.exe

>While it turned out to be important AND undocumented that VS needs "Visual Studio extension development" extension I have the feeling
> that MSVC folder content was created only after "Desktop development with C++ " installation in VS => right? Should be in docu as well.

The missing assembly probably comes with any other "workload" aswell as it is used by most project wizars. It's true that "C++ development" is expected so far, I wasn't aware that you could almost get something working without that.

--

https://issues.dlang.org/show_bug.cgi?id=19624

Marc Bach <marc.arnold.bach@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WORKSFORME

--- Comment #2 from Marc Bach <marc.arnold.bach@gmail.com> ---
Ha! This is crazy cool!

Three aspects:

1) Problem solved!

2)Incredible fast support ... I feel like a premium customer :o)

3) I came for D only.. I am a Ruby/Java guy that's why I start from scratch with no visual studio, no C++.

If the installation requires secret knowhow or is assuming magic installed c++
settings it is difficult.
I would have abandoned visualD to early just because of docu... and that would
have been a pity because I found no debugger like here in linux.

--

https://issues.dlang.org/show_bug.cgi?id=19624

--- Comment #3 from Rainer Schuetze <r.sagitario@gmx.de> ---
Good to hear it works. Yeah, the debugger is a major selling point of VS.

The documentation is easy to fall behind, it should better focus on the newer versions of VS. VS2019 is already around the corner, though. I'll give it an update before the next release.

--