Henrik Fransas
Optimizely
Mar 18, 2016
visibility 5224
star star star star star
(3 votes)

Using AppSettings instead of ConfigSections for Episerver Find

In the documentation for Episerver Find it says that you should write like this in your app.config or web.config file:

<configuration>
     <configSections>
            <section
            name="episerver.find"
            type="EPiServer.Find.Configuration, EPiServer.Find" requirePermission="false"/>
        </configSections>
        <episerver.find
            serviceUrl="http://..."
        defaultIndex="myindex"/>
</configuration>

There also exist another way to set this up that are a little hidden, and that are to go through the appsettings in the config file. So instead of writing like the above you can write like this:

<appSettings>
    <add key="episerver:FindServiceUrl" value="http://..." />
    <add key="episerver:FindDefaultIndex" value="myindex" />
  </appSettings>
  

Depending on how you have set up you deployment pipeline this could be a nice way since it is easier to implement config transformation for this I think.

Mar 18, 2016

Comments

Vincent
Vincent Mar 22, 2016 04:40 AM

Good to know :)

For my current project, I remove the element first, then insert with different index key 


Henrik Fransas
Henrik Fransas Mar 22, 2016 07:57 AM

That is true!

Missed to inform about that. Thanks!

Jonas Carlbaum
Jonas Carlbaum Oct 22, 2018 08:57 AM

@episerver please update the documentation about *Staged deployments* settings in https://world.episerver.com/documentation/developer-guides/CMS/Deployment/deployment-scenarios/Deploying-to-Azure-webapps/#StagedDeployment to inform about how to enable a separate Find-index on Deployment slots.

error Please login to comment.
Latest blogs
Surviving a Dirty Feed. Part 3: Error Handling and Event Batching

Committing a 250,000-row Optimizely catalog import row by row, returning a per-row failure report, and coalescing catalog events into one per batch.

Stanisław Szołkowski | Oct 16, 2026 |

Building UI Extensions for Optimizely SaaS CMS

Introduction Developers have been extending the functionality of Optimizely PaaS CMS for years using addons built in C# and deployed as NuGet...

Mark Stott | Oct 15, 2026

Cheapskate AI Translator: Because Translation Should Not Require a Second Mortgage

There is a particular kind of software project that begins with a detailed architecture document, a product roadmap, and a carefully assembled...

Linh Doan Cuu | Oct 15, 2026

Computed Fields in CMS 13 Content Contracts with Optimizely Graph

Content Contracts in Optimizely CMS 13 allow different content types to share a common structure when querying Optimizely Graph. But what if the...

Mardy | Oct 14, 2026