Practical overview
When it fits
Use it when a .NET application needs an embedded, in-memory text-vector store for semantic search or RAG retrieval.
Who it is for
- Developers adding semantic text search to .NET applications.
- Teams building RAG workflows that need to retrieve text context for language-model prompts.
Documented uses
- Store and search text using vector representations within a .NET application.
- Retrieve relevant text to supply as context in a RAG workflow.
- Choose among supported local, OpenAI or Ollama embedding approaches.
Requirements & limits
The project is distributed as the Build5Nines.SharpVector NuGet package and identifies an MIT license.
- .NET 8 or later is identified as the framework requirement.
- The library uses in-memory storage, a different design choice from a separate database-based vector store.
- Local, OpenAI and Ollama embeddings are listed as supported.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Add chunked text to an in-memory SharpVector database
Load a document into a BasicMemoryVectorDatabase by splitting it into chunks and assigning metadata.
Before you start
- A .NET project using SharpVector.
- Document text to load.
- A metadata value for each chunk; the documented example creates a JSON string.
Steps
Import
Build5Nines.SharpVectorandBuild5Nines.SharpVector.Data.Create the database with
var vdb = new BasicMemoryVectorDatabase();.Create a loader with
var loader = new TextDataLoader(vdb);.Call
loader.AddDocumentwith the document text andTextChunkingOptions, choosing a documented method such asParagraph,Sentence,FixedLength, orOverlappingWindow, and provideRetrieveMetadatafor each chunk.
Expected outcome
The document is split according to the selected strategy and its chunks are loaded into the in-memory vector database with metadata stored alongside them.
Guide limitations
- Each chunk must have metadata, even if it is only a minimal description.
- Chunking strategy and size should be selected for the content and retrieval goals; experimentation may be needed.
- For larger documents, the documentation says chunking is required for the best semantic search results.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 12 October 2026
- Original website title
- Build5Nines/SharpVector · Official homepage title · retained in its source language

