This repository was archived by the owner on Feb 25, 2026. It is now read-only.
Remove .NET Standard Code from Repo #4382
Copy link
Copy link
Closed
Labels
.NETComponents which are .NET based (non UWP specific)Components which are .NET based (non UWP specific)CI/pipeline 🔬Completed 🔥build 🔥
Milestone
Description
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!
Metadata
Metadata
Assignees
Labels
.NETComponents which are .NET based (non UWP specific)Components which are .NET based (non UWP specific)CI/pipeline 🔬Completed 🔥build 🔥
Type
Projects
- StatusShow more project fieldsDone
Activity
Sergio0694 commentedon Nov 15, 2021
@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.1I guess? 🤔Yes, we can simplify tests a whole lot like I did in the
dotnetrepo 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
dotnetand I think there's plenty of room for improvements here too now 🎉michael-hawker commentedon Nov 15, 2021
@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.