Skip to content
This repository was archived by the owner on Feb 25, 2026. It is now read-only.

Remove .NET Standard Code from Repo #4382

Closed

Description

@michael-hawker

Describe the problem this feature would solve

We've moved our .NET Standard Code to now be the .NET Community Toolkit. 🎉🎉🎉

Its new home is now in this repo here.

Describe the solution

We migrated all the history over there as well, so now we just need to remove the following packages from our repo to complete the transfer:

  • Microsoft.Toolkit
  • Microsoft.Toolkit.Diagnostics
  • Microsoft.Toolkit.HighPerformance
  • Microsoft.Toolkit.Mvvm
  • Microsoft.Toolkit.Mvvm.SourceGenerators

For anything that depends on Microsoft.Toolkit still we should update it to grab the CommunityToolkit.Common package from the MainLatest feed instead.

I believe we can also simplify our tests a bit potentially, right @Sergio0694?

@XAML-Knight mind taking a stab at opening a PR for this migration step removing these packages here in this repo? Thanks!

Activity

  1. Sergio0694 commented on Nov 15, 2021

    @Sergio0694
    Member

    @michael-hawker Just to double check, we do plan to hold on this until we push 7.1.2 out, correct?
    Otherwise we'll have no way to do so, unless we branched off of rel/7.1.1 I guess? 🤔

    "I believe we can also simplify our tests a bit potentially, right @Sergio0694?"

    Yes, we can simplify tests a whole lot like I did in the dotnet repo as well.
    We can remove all the shared projects and just aggregate the UWP test projects, for instance, and do some cleanup.
    The infrastructure is extremely clean now for dotnet and I think there's plenty of room for improvements here too now 🎉

  2. michael-hawker commented on Nov 15, 2021

    @michael-hawker
    MemberAuthor

    @Sergio0694 we can pick up an intermediate build at the moment, but yes we'd base off of 7.1.2 eventually. If you plan to put that together this week, then we can coordinate too, especially if we update for WinUI 3 1.0. FYI @azchohfi.

  3. ghost locked as resolved and limited conversation to collaborators on Feb 1, 2022
  4. added this to the 7.1.3 milestone on Aug 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions