microsoft/vs-validation

.NET Core SDK adoption blockers

AArnott opened this issue · 0 comments

AArnott commented

This issue tracks the adoption blocker issues to switching to the .NET Core project system in VS2017:

Functional issues

  • dotnet/Nerdbank.GitVersioning#93 Nerdbank.GitVersioning interop with .NET SDK
  • dotnet/sdk#703 DocumentationFile cannot be set in project file
  • dotnet/sdk#651 AssemblyInfo.cs should not be generated on package restore
  • XLF -> resx generation support (ideally via full Multilingual App Toolkit support)
  • ReadOnlySourceTree package support in and for .NET SDK
  • MicroBuild signing plugin support in and for .NET SDK
  • Get unit tests running at least on net45 if not also netcoreapp1.0
  • Verify that pdbgit works properly
  • novotnyllc/MSBuildSdkExtras#6 Get nupkg lib folders right.
  • Must be able to run Microsoft ship requirement set of FxCop rules (FxCop port)
  • Totally portable toolset so it can run without VS2017 installation, or VS2017 installed on MicroBuild agents

Reliability issues

  • dotnet/roslyn#16410 VS crashes on open of .NET Core projects far too frequently
  • dotnet/roslyn#16673 VS crashes when SolutionCreator.UpdateDocumentAsync gets NullReferenceException back over jsonrpc
  • NuGet/Home#4289 PackTask frequently fails with file access conflict

Non-blocking (because some workaround exists) but tracking