Skip to content

[VMR] Publish all Roslyn packages from the VMR #78297

Open
0 of 3 issues completed
Open
Epic
0 of 3 issues completed
@dibarbet

Description

@dibarbet

.NET is moving over to the VMR. Currently Roslyn is publishing packages as part of our official build, both manually to vs-impl and VSSDK, as well as using darc (to dotnet-tools as an intermediate). We also manually publish to nuget.org when VS releases.

In order to standardize our package publishing, we should switch over to the VMR for publishing packages for .NET 10. There are a few tasks to take care of here

  1. We need to ensure the VMR fully builds all of Roslyn and its nuget packages
    a. We need to correctly mark all Roslyn packages that go to nuget.org as IsShipping or not
    b. This includes packages we have historically pushed to nuget ourselves (that have VS dependencies that need to be updated after VS ships)
  2. Roslyn will start creating packages in its official build with the -vs suffix. These packages will only be used to insert into VS. We’ll continue to use darc to push these to intermediate feeds.
  3. Roslyn will update to not manually publish to vs-impl/vssdk feeds. Instead those should reference dotnet-tools as an upstream to pull in the latest packages pushed from the VMR.

Sub-issues

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area-InfrastructureuntriagedIssues and PRs which have not yet been triaged by a lead

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions