BigPhil

My feedback

  1. 7 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  SQL Server » Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    BigPhil commented  · 

    I managed to get around this problem by creating a symlink on our build server, in folder C:\Program Files (x86)\Microsoft Visual Studio\2017, using the following command, from an elevated command prompt:

    mklink /D Professional "c:\Program Files (x86)\Microsoft Visual Studio 14.0"

    BigPhil supported this idea  · 

Feedback and Knowledge Base