22 packages returned for Tags:"Indexing"

Provides extension methods to Entity Framework for simplified fluent configuration of indexes.

Deprecated, see Structurizer instead: https://www.nuget.org/packages/Structurizer/ PineCone takes an instance of an C# class and builds a class-schema for it. This schema is then used to extract all primitive .Net types in the object-graph using some IL-Emits and then turns this to a key-value... More information

Dynamicweb 9 package that contains the API used for implementation of indexing, querying and storing of settings related to the search engine in Dynamicweb.

LIFTI provides a simple API that allows you to build a searchable full text index. This can be useful for document retrieval or simply allowing .NET objects to be searched for by associated text.

Index support for Service Fabric stateful services and reliable collections.

Scalability stuff.

A keyword indexing framework for Entity Frameword

A keyword indexing framework

Provides a simple API to use Lucene.NET with objects without having previous knowledge of indexing

The Intellidact API provides a flexible and powerful way for .NET developers to interface with the Intellidact redaction engine via the Universal Web Service (UWS).

General library for the sensenet platform containing interfaces and indexing-related classes.

Lucene29 library for the sensenet platform containing the core indexing layer that works with Lucene index files directly.

Lucene29 Local library for the sensenet platform containing the Lucene-based local indexing and query engine implementations.

Indirect indexing collection.

Lucene29 Common library for the sensenet platform containing server-side elements, most importantly the generic search engine.

Json Transformer

Tiny Fast Json Parser Support Multiple Indexing, Json Object And Json Array.

The Apache Software Foundation Lucene.Net a full-text search engine library. This version is a fork of the original Lucene.Net code for the sensenet platform.

Index modular/rendered content added to a page via Sitecore Experience Editor. Determine which renderings should be indexed based on patch config. All logic broken out into Sitecore pipelines to provide customization support.

Allows the customization of where indexes start in C#. Not only can you force Roslyn to interpret items[1] as items[0], but also items[-42] and items[1_000_000] if you want! The sky (and common sense) are the only limits!