Difficulty / est. effort: large, exploratory (new project + toolchain)
Context: Beyond the MCP recipes (which only wire the assistant to okf-mcp), a native Visual Studio extension (VSIX) would let .NET developers browse, validate, and navigate an OKF bundle directly inside Visual Studio — the IDE our primary audience already lives in. This is a larger, exploratory feature; please discuss the design in a Discussion or on this issue before a large PR.
Scope (proposal — refine in discussion):
- A new extension project (e.g.
src/OKF4net.VisualStudio/, a VSIX targeting VS 2022) that references the zero-dependency OKF4net core library.
- Minimum viable surface: a command / tool window that runs
BundleValidator.Validate on the current bundle and shows severity-tagged diagnostics in the Error List, and a simple bundle/concept tree view.
- Reuse the core library and (optionally) the
okf CLI; do not reimplement OKF logic.
Hard rules: the VSIX project may use the VS SDK tooling packages it needs — that does not affect the core library's zero-third-party-runtime-dependency guarantee (the extension is a separate project). Do not add runtime dependencies to src/OKF4net/ or src/OKF4net.Cli/. Never modify tests/fixtures/.
How to verify: the extension builds to a .vsix, loads in a VS experimental instance, and its validate command reports the same diagnostics as okf validate on the same bundle.
Good to know: Start small and iterate; a validate-only MVP is a great first cut. See CONTRIBUTING.md. Marketplace publishing can come later.
Difficulty / est. effort: large, exploratory (new project + toolchain)
Context: Beyond the MCP recipes (which only wire the assistant to
okf-mcp), a native Visual Studio extension (VSIX) would let .NET developers browse, validate, and navigate an OKF bundle directly inside Visual Studio — the IDE our primary audience already lives in. This is a larger, exploratory feature; please discuss the design in a Discussion or on this issue before a large PR.Scope (proposal — refine in discussion):
src/OKF4net.VisualStudio/, a VSIX targeting VS 2022) that references the zero-dependencyOKF4netcore library.BundleValidator.Validateon the current bundle and shows severity-tagged diagnostics in the Error List, and a simple bundle/concept tree view.okfCLI; do not reimplement OKF logic.Hard rules: the VSIX project may use the VS SDK tooling packages it needs — that does not affect the core library's zero-third-party-runtime-dependency guarantee (the extension is a separate project). Do not add runtime dependencies to
src/OKF4net/orsrc/OKF4net.Cli/. Never modifytests/fixtures/.How to verify: the extension builds to a
.vsix, loads in a VS experimental instance, and its validate command reports the same diagnostics asokf validateon the same bundle.Good to know: Start small and iterate; a validate-only MVP is a great first cut. See CONTRIBUTING.md. Marketplace publishing can come later.