Repository navigation
.NET: Add vectorstore community projects - #9414
westey (westey-m) merged 1 commit into
Conversation
There was a problem hiding this comment.
🟡 Changes recommended
The catalog must retain its required per-provider scenarios column and preserve Chroma’s hybrid-search scenario.
1 open finding
What changed in this PR
Expands the .NET community catalog to help users discover external vector-store integrations.
Changes:
- Adds 12 providers with package and issue-reporting links.
- Moves shared memory and retrieval scenarios above the provider table.
| File | Description |
|---|---|
dotnet/samples/community-projects.md |
Expands vector-store listings and reorganizes scenario documentation. |
🧠 Review effort: Balanced
There was a problem hiding this comment.
MAF Automated Review — Iteration 1
Result: Findings reported
Scope: full PR (1 commit(s)): 5456fe4fe325
Model: gpt-5.6-sol
Overview
The PR expands the .NET community catalog with alphabetized, package-specific project links and direct external issue-creation URLs while retaining the required non-endorsement disclaimer. However, the revised table removes the catalog contract's mandatory per-project Scenarios field and drops an existing Chroma capability, leaving one publishable documentation-contract issue.
Reviewed the supplied pull-request change set across correctness, security/reliability, architecture, and failure behavior.
1 verified finding remained after source verification (1 medium) across 1 file. Details are attached to the affected lines below.
Affected areas: dotnet/samples/community-projects.md

Motivation & Context
Description & Review Guide
Update the community projects md with all known vector store community packages.
Related Issue
Fixes #
AI Assistance
AI assistance details:
Contribution Checklist
breaking changelabel (or add "[BREAKING]" to the title prefix, before or after any language prefix) — a workflow keeps the label and title prefix in sync automatically.