Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
AI OnAI Off
Navigation [hide]
[expand]
- Architecture
- DotNET Client API
- Client class
- Inheritance and interfaces
- Indexing
- Getting documents
- Deleting documents
- File attachments
- Searching
- Auto Boosting
- Best Bets
- Sorting
- Boosting with filters
- Boosting with weights
- Facets
- Filtering
- Strings
- Numerical
- DateTime
- Boolean
- Enum
- Filter and FilterHits
- Complex objects
- Custom filtering methods
- Free text search
- Geo Search
- Highlighting
- Including documents matching a filter
- More Like/Related
- Multiple searches in one request
- Searching over multiple types
- Pagination
- Languages
- Projections
- Related Queries
- Synonyms
- Unified search
- Caching
- Nested queries
- Connectors
- Customizing serialization
- Integration
- Episerver Commerce-Find integration
- Episerver 7.5+
- Access rights
- Customized search block styling guide
- Filters
- GetContentResult and GetFilesResult
- Indexing content in a content area
- Indexing
- Logging
- Querying examples
- Related content and dependencies
- Scheduled job for indexing
- Episerver 7/7.5 CMS
- Access rights
- Filters
- GetContentResult and GetFilesResult
- Indexing content in a content area
- Indexing
- Logging
- Querying examples
- Related content and dependencies
- Scheduled job for indexing
- Episerver CMS 6 R2
- Access rights CMS 6 R2
- GetPagesResult and GetFilesResult
- Indexing CMS 6 R2
- Logging CMS 6 R2
- Querying examples CMS 6 R2
- Related pages and dependencies
- Scheduled job for indexing CMS 6 R2
- Shell module
- Search statistics
Area:
Optimizely Search & Navigation
ARCHIVED This content is retired and no longer maintained. See the latest version here.
Integration
The Episerver integration builds on the .NET client API, adding functionality for automatically indexing objects, and methods for filtering, retrieving, and caching results. This topic describes how to integrate Episerver Find with your solution.
Installation
To use the Episerver integration, you need the Episerver Find .NET API and these assemblies:
- Episerver.Find.Framework.dll
- EPiServer.Find.Cms.dll
The assemblies are installed from the Episerver NuGet feed (on http://nuget.episerver.com/feed/packages.svc/). Install the packages using NuGet, as described in Installing Episerver updates.
Reference all assemblies in your project, and add the standard configuration for the .NET API to web.config.
SearchClient.Instance
When working with the general .NET API, you typically create an instance of the IClientclass using the Client.CreateFromConfig method. Following the general pattern of Episerver development, the Episerver integration provides a singleton instance in the form of the SearchClient class and its Instance property. The returned instance is a regular IClient, but some modifications are made to it at start up. In other words, when working with Episerver and Episerver Find, be sure to use SearchClient.Instance.
Related topics
Last updated: Nov 16, 2015
