Which Visual Studio SDK version is compatible with an up-to-date Roslyn version?

[drauch]

I try to use the NuGet packages "Microsoft.VisualStudio.SDK" and "Microsoft.VisualStudio.LanguageServices" in combination with an up-to-date Roslyn version, i.e., with the packages "Microsoft.CodeAnalysis.CSharp.Workspaces" 3.8.0 as well as "Microsoft.CodeAnalysis.Workspaces.MSBuild" 3.8.0.

However, I run into NuGet package warnings when building the project and we have a strict no-warning policy in our company.

I tried various combinations (downgrading the SDK, downgrading the Roslyn packages, etc.) but I have not found a single combination which works together.

I think I'm doing something wrong here, because I cannot be the only one trying to use the VS SDK package in combination with Roslyn?!

Please point me out a working packages combination, thank you.

Best regards,
D.R.

[jmarolf]

What is the warning you are getting? Microsoft.CodeAnalysis.CSharp.Workspaces has no dependencies on visual studio packages and Microsoft.CodeAnalysis.Workspaces.MSBuild requires 15.3 or newer of the Microsoft.Build.Framework. Both of which should be easily resolved.

I get no warnings for a console app that references these packages.

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net472</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.CodeAnalysis.CSharp.Workspaces" Version="3.8.0" />
    <PackageReference Include="Microsoft.CodeAnalysis.Workspaces.MSBuild" Version="3.8.0" />
    <PackageReference Include="Microsoft.VisualStudio.SDK" Version="16.0.206" />
  </ItemGroup>

</Project>

Please:

• post the text of the warning you are getting from nuget restore
  OR
• create a binary log from a build (instructions here and upload it to this discussion.

[drauch]

You should be able to explicitly reference each of those packages to resolve the warnings.

Explicitly referencing those, runs into 10 more problems. This goes on and on, I stopped after adding about 10 packages. Isn't the SDK package all about referencing only ONE package anymore and not referencing 1000?

Best regards,
D.R.

PS: Do you still need a repro, or are you fine with @PathogenDavid 's?

[jmarolf]

ah, sorry I see the issue between Microsoft.VisualStudio.LanguageServices and Microsoft.VisualStudio.SDK

Specifically referencing the latest StreamJsonRpc will ensure all the correct json assemblies are made primary.

Microsoft.VisualStudio.LanguageServer.Client and Microsoft.VisualStudio.LanguageServer.Protocol will fix the remaining warnings (I will need to look into why these references don't work).

This gives me no warnings:

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net472</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.CodeAnalysis.CSharp.Workspaces" Version="3.8.0" />
    <PackageReference Include="Microsoft.CodeAnalysis.Workspaces.MSBuild" Version="3.8.0" />
    <PackageReference Include="Microsoft.VisualStudio.LanguageServer.Client" Version="16.8.146" />
    <PackageReference Include="Microsoft.VisualStudio.LanguageServer.Protocol" Version="16.8.146" />
    <PackageReference Include="Microsoft.VisualStudio.LanguageServices" Version="3.8.0" />
    <PackageReference Include="Microsoft.VisualStudio.SDK" Version="16.0.206" />
    <PackageReference Include="StreamJsonRpc" Version="2.6.121" />
  </ItemGroup>

</Project>

[drauch]

Using those dependencies runs into 10 new errors:

         C:\Development\MyProject\MyProject.VSIntegration\MyProject.VSIntegration.csproj : error NU1603: Microsoft.CodeAnalysis.EditorFeatures.Text 3.8.0 depends on Microsoft.VisualStudio.CoreUtility (>= 16.8.39) but Microsoft.VisualStudio.CoreUtility 16.8.39 was not found. An approximate best match of Microsoft.VisualStudio.CoreUtility 16.8.239 was resolved. [C:\Development\MyProject\MyProject.sln]
         C:\Development\MyProject\MyProject.VSIntegration\MyProject.VSIntegration.csproj : error NU1603: Microsoft.VisualStudio.LanguageServer.Client 16.8.146 depends on Microsoft.VisualStudio.CoreUtility (>= 16.8.147) but Microsoft.VisualStudio.CoreUtility 16.8.147 was not found. An approximate best match of Microsoft.VisualStudio.CoreUtility 16.8.239 was resolved. [C:\Development\MyProject\MyProject.sln]
         C:\Development\MyProject\MyProject.VSIntegration\MyProject.VSIntegration.csproj : error NU1603: Microsoft.VisualStudio.Shell.Framework 16.7.30329.88 depends on Microsoft.VisualStudio.OLE.Interop (>= 7.10.6072) but Microsoft.VisualStudio.OLE.Interop 7.10.6072 was not found. An approximate best match of Microsoft.VisualStudio.OLE.Interop 16.7.30328.74 was resolved. [C:\Development\MyProject\MyProject.sln]
         C:\Development\MyProject\MyProject.VSIntegration\MyProject.VSIntegration.csproj : error NU1603: Microsoft.VisualStudio.Shell.Framework 16.7.30329.88 depends on Microsoft.VisualStudio.SDK.Analyzers (>= 16.7.8) but Microsoft.VisualStudio.SDK.Analyzers 16.7.8 was not found. An approximate best match of Microsoft.VisualStudio.SDK.Analyzers 16.7.9 was resolved. [C:\Development\MyProject\MyProject.sln]
         C:\Development\MyProject\MyProject.VSIntegration\MyProject.VSIntegration.csproj : error NU1603: Microsoft.VisualStudio.LanguageServer.Client 16.8.146 depends on Microsoft.VisualStudio.Shell.Framework (>= 16.7.30204.53-pre) but Microsoft.VisualStudio.Shell.Framework 16.7.30204.53-pre was not found. An approximate best match of Microsoft.VisualStudio.Shell.Framework 16.7.30329.88 was resolved. [C:\Development\MyProject\MyProject.sln]
         C:\Development\MyProject\MyProject.VSIntegration\MyProject.VSIntegration.csproj : error NU1603: Microsoft.CodeAnalysis.EditorFeatures.Text 3.8.0 depends on Microsoft.VisualStudio.Text.Data (>= 16.8.39) but Microsoft.VisualStudio.Text.Data 16.8.39 was not found. An approximate best match of Microsoft.VisualStudio.Text.Data 16.8.239 was resolved. [C:\Development\MyProject\MyProject.sln]
         C:\Development\MyProject\MyProject.VSIntegration\MyProject.VSIntegration.csproj : error NU1603: Microsoft.CodeAnalysis.EditorFeatures.Text 3.8.0 depends on Microsoft.VisualStudio.Text.Logic (>= 16.8.39) but Microsoft.VisualStudio.Text.Logic 16.8.39 was not found. An approximate best match of Microsoft.VisualStudio.Text.Logic 16.8.239 was resolved. [C:\Development\MyProject\MyProject.sln]
         C:\Development\MyProject\MyProject.VSIntegration\MyProject.VSIntegration.csproj : error NU1603: Microsoft.VisualStudio.SDK.Analyzers 16.7.9 depends on Microsoft.VisualStudio.Threading.Analyzers (>= 16.7.40) but Microsoft.VisualStudio.Threading.Analyzers 16.7.40 was not found. An approximate best match of Microsoft.VisualStudio.Threading.Analyzers 16.7.54 was resolved. [C:\Development\MyProject\MyProject.sln]
         C:\Development\MyProject\MyProject.VSIntegration\MyProject.VSIntegration.csproj : error NU1603: Microsoft.VisualStudio.LanguageServer.Client 16.8.146 depends on Microsoft.VisualStudio.Utilities (>= 16.7.30203.189-pre) but Microsoft.VisualStudio.Utilities 16.7.30203.189-pre was not found. An approximate best match of Microsoft.VisualStudio.Utilities 16.7.30329.38 was resolved. [C:\Development\MyProject\MyProject.sln]
         C:\Development\MyProject\MyProject.VSIntegration\MyProject.VSIntegration.csproj : error NU1603: Microsoft.VisualStudio.RemoteControl 16.3.23 depends on Microsoft.VisualStudio.Utilities.Internal (>= 16.3.5) but Microsoft.VisualStudio.Utilities.Internal 16.3.5 was not found. An approximate best match of Microsoft.VisualStudio.Utilities.Internal 16.3.23 was resolved. [C:\Development\MyProject\MyProject.sln]

(If it's important, maybe it is, I also need to reference NuGet.VisualStudio - currently using v 5.8.0)

[MaceWindu]

That's a long standing issue. For some reason a lot of MS packages (mostly VS-related) published to nuget referencing unpublished (internal?) versions of other packages and nothing done to fix this (I reported it once to support, which resulted in new package with even more broken dependencies...). This issue contains a lot of examples of such packages

[drauch]

So you're saying we can't really us the Microsoft.VisualStudio.SDK package but instead have to pinpoint the versions of all dependencies (like 40 or so) in our csproj? That sucks...

[drauch]

It looks like the following csproj file works:

  <ItemGroup>
    <PackageReference Include="Microsoft.VisualStudio.LanguageServices" Version="3.8.0" />
    <PackageReference Include="Microsoft.VisualStudio.SDK" Version="16.0.206" />
    <PackageReference Include="Microsoft.VisualStudio.SDK.EmbedInteropTypes" Version="15.0.36" />
    <PackageReference Include="NuGet.VisualStudio" Version="5.8.0" />
  </ItemGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.VisualStudio.CoreUtility" Version="16.8.239" />
    <PackageReference Include="Microsoft.VisualStudio.Imaging.Interop.14.0.DesignTime" Version="16.7.30328.74" />
    <PackageReference Include="Microsoft.VisualStudio.Shell.Interop.15.3.DesignTime" Version="16.7.30328.74" />
    <PackageReference Include="Microsoft.VisualStudio.Shell.Interop.15.6.DesignTime" Version="16.7.30328.74" />
    <PackageReference Include="Microsoft.VisualStudio.LanguageServer.Client" Version="16.8.146" />
    <PackageReference Include="Microsoft.VisualStudio.LanguageServer.Protocol" Version="16.8.146" />
    <PackageReference Include="Microsoft.VisualStudio.OLE.Interop" Version="16.7.30328.74" />
    <PackageReference Include="Microsoft.VisualStudio.SDK.Analyzers" Version="16.7.9" />
    <PackageReference Include="Microsoft.VisualStudio.Shell.15.0" Version="16.7.30329.88" />
    <PackageReference Include="Microsoft.VisualStudio.Shell.Framework" Version="16.7.30329.88" />
    <PackageReference Include="Microsoft.VisualStudio.Shell.Interop.14.0.DesignTime" Version="16.7.30328.74" />
    <PackageReference Include="Microsoft.VisualStudio.Shell.Interop.9.0" Version="16.7.30328.74" />
    <PackageReference Include="Microsoft.VisualStudio.Text.Data" Version="16.8.239" />
    <PackageReference Include="Microsoft.VisualStudio.Text.Logic" Version="16.8.239" />
    <PackageReference Include="Microsoft.VisualStudio.Threading" Version="16.8.55" />
    <PackageReference Include="Microsoft.VisualStudio.Threading.Analyzers" Version="16.8.55" />
    <PackageReference Include="Microsoft.VisualStudio.Utilities" Version="16.7.30329.38" />
    <PackageReference Include="Microsoft.VisualStudio.Utilities.Internal" Version="16.3.23" />
    <PackageReference Include="Nerdbank.Streams" Version="2.6.81" />
    <PackageReference Include="StreamJsonRpc" Version="2.6.121" />
    <PackageReference Include="System.IO.Pipelines" Version="4.7.3" />
  </ItemGroup>

However, the whole second ItemGroup - I don't want it, and it feels bad too. Hope you can fix this soon :)

Best regards,
D.R.