Skip to content
This repository was archived by the owner on Feb 25, 2026. It is now read-only.
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

Closed

Description

@michael-hawker

Describe the problem this feature would solve

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 ...???

Describe alternatives you've considered

Additional context & Screenshots

Activity

  1. added this to the future milestone on May 6, 2020
  2. modified the milestones: future, 7.0 on Jun 23, 2020
  3. michael-hawker commented on Sep 21, 2020

    @michael-hawker
    MemberAuthor

    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.

  4. Nirmal4G commented on Mar 6, 2021

    @Nirmal4G
    Contributor

    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.

  5. modified the milestones: 7.0, 7.1 on Mar 9, 2021
  6. modified the milestones: 7.1, 7.2/8.0? on Aug 31, 2021
  7. locked and limited conversation to collaborators on Jul 29, 2022
  8. converted this issue into a discussion #4661 on Jul 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions