You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 25, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 25, 2026. It is now read-only.
[Repo] Create Solution Filters or some solution for managing size of toolkit #3270
The toolkit is huge. We tried breaking out the graph controls, but that caused it's own issues with dependencies. We need a solution which allows us to build the toolkit in its entirety, but at the same time make it easier to have a fast dev cycle for development of specific components be it .NET specific, a certain control, etc...
Ideally too the sample app should be also able to be loaded with just a single sample so that it can be built/run quickly just like creating a file new project would. This would encourage easier integrations in the toolkit from the start when working on new things vs. an afterthought or extra work from copying things over from a new project template.
Describe the solution
??? Not sure if git submodules make sense or solution filters or some other system ...???
We'd also talked about having a sub-module to our documentation repo to make it easier to include/validate docs within the sample app rather than requiring our current 'special' convention.
I propose we should reorganize the repository with all the consumer projects that @windows-toolkit have. I don't know why you split them in the first place!! If we do want to split into several repos, at least split them according to target platform like UWP, Win32 and Pure .NET or component-wise like Microsoft Graph, Xaml Islands, etc...
I have a few ideas on repo structure that should help us at managing them better. I'll try them to see what works better and post the tree output here. Then we can decide which one is better for the toolkit repository. But before that I need to know if we're going for the monorepo or not.
Activity
michael-hawker commentedon Sep 21, 2020
We'd also talked about having a sub-module to our documentation repo to make it easier to include/validate docs within the sample app rather than requiring our current 'special' convention.
Nirmal4G commentedon Mar 6, 2021
I propose we should reorganize the repository with all the consumer projects that @windows-toolkit have. I don't know why you split them in the first place!! If we do want to split into several repos, at least split them according to target platform like
UWP,Win32andPure .NETor component-wise likeMicrosoft Graph,Xaml Islands, etc...I have a few ideas on repo structure that should help us at managing them better. I'll try them to see what works better and post the
treeoutput here. Then we can decide which one is better for the toolkit repository. But before that I need to know if we're going for the monorepo or not.