-
Notifications
You must be signed in to change notification settings - Fork 80
Quick Start
Niels Laute edited this page Dec 6, 2024
·
6 revisions
Warning: Try not to clone the repo into any location where the path is already significantly long. There is a windows an existing MAX path issue with windows (Files on paths longer than 256 cannot be found be the build tool chain). Within the project there are paths of 190 characters, so the shorter the base directory the better.
git clone --recurse-submodules https://github.com/CommunityToolkit/Windows.git
Ensure that MSBuild is on your PATH, then run GenerateAllSolution.bat
from the root directory. When solution generation is complete, Visual Studio will open automatically with the solution loaded.
With the desired platform selected as the startup project, you're ready to build components and samples, run tests, or build and deploy the gallery app for the Community Toolkit.
- Navigate to a specific component, e.g.
..\Windows\components\SettingsControls
- Run
OpenSolution.bat
to generate the solution and project heads - Open the solution (e.g.
SettingsControls.sln
- In Visual Studio, select your preferred project head (UWP, WinAppSDK or WASM) and hit F5:
- Home π
- Welcome π
- Principles βοΈ
- Roadmap πΊ
- .NET Foundation
- Why Microsoft supports this project
- License π
- Getting Started π
- Sample App π±
- NuGet Packages π¦
- Preview Packages π
- Toolkit Labs π§ͺ
- Questions β
- Discussions π₯
- Submitting an Issue βοΈ
- Good First Issue π
- Help Wanted π
- Bug Fixes π
- Feature Requests π«
- Create and Submit PullRequest π
- Documentation π
- Review PR π
- Avoid Roadblocks π§
- Required Dependencies π
- Quick Start β‘
- Sample Development π±
- Testing π§ͺ
- Accessibility Guideline βΏ
- Coding Style and Conventions β
- Building XAML Controls π
- CI and Infrastructure πΎ
- Updating ToolkitLabs.dev π
- Migration Guide from v7 to v8 π
- How the Project is Organized ποΈ
- Join the Toolkit Organization πͺ
- Hall of Fame π