How heku/kool.editproject works
Project type and purpose
• This is an open-source Visual Studio extension (VSIX) that adds “Edit Project File” and “Edit Solution File” context-menu commands inside the VS IDE.
• It targets two host environments: Visual Studio 2019 and Visual Studio 2022.
File structure
• Top-level solution (Kool.EditProject.sln) contains three main projects:
• Kool.EditProject.2019 (VSIX project for VS2019)
• Kool.EditProject.2022 (VSIX project for VS2022)
• Kool.EditProject.Shared (class library with all shared commands, models, pages, resources)
• The “Linked” folder holds common assets (VSCT menu definitions, localization templates) that both VSIX projects consume.
• Build & CI/CD: azure-pipelines.yml drives build, vsix.psm1 and publish.manifest.{2019,2022}.json control packaging and publishing to the Marketplace.
• README and Screenshots document features and UI flows.
README for additional insights
• Confirms feature set (single/multiple project editing, solution editing, configurable options).
• Mentions known issue around overlapping “Edit” menus in .NET Core projects.
• Points to Azure DevOps build badge and Marketplace badges for each target.
Diagramming the architecture
• VSIX Project “Kool.EditProject.2019”
• VSIX Project “Kool.EditProject.2022”
• Shared Library “Kool.EditProject.Shared”
• “Kool.EditProject.Linked” assets (menus, localization)
• Visual Studio Host (2019 & 2022 processes)
• Azure DevOps build pipeline & Marketplace publishing
b. Relationships and interactions
• Both VSIX projects reference the Shared library and Linked assets.
• At runtime, VS loads the VSIX package → invokes command registrations from Shared.
• UI flows: user right-clicks project/solution → VS triggers command → Shared code launches the XML editor window.
• CI pipeline pulls code → builds all projects → produces two VSIX bundles → publishes to respective Marketplace endpoints.
c. Architectural patterns & principles
• Modular packaging: thin version-specific wrappers referencing a single shared core.
• Separation of concerns: Commands, Models, UI (Pages), and localization in distinct namespaces/folders.
• Resource linking: shared VSCT files and .resx resources kept in Linked folder to avoid duplication.
d. Key technologies & frameworks
• C#/.NET Framework (VS SDK)
• Visual Studio Extensibility (VSIX, .vsct)
• MSBuild / .csproj multi-targeting
• Azure DevOps (YAML pipelines)
• PowerShell (vsix.psm1) and JSON manifests for publishing