Henrik Fransas
Mar 18, 2016
visibility 5133
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
Order tabs with drag and drop V2

I earlier did a very simple Blazor version to be able to sort tabs with drag and drop. I wanted to update it a bit and also display how the tabs ar...

Per Nergård (MVP) | Aug 4, 2026

Optimizely : Missing Language Manager Gadget Fix in CMS 12 After Upgrading to .NET 10

Recently, while upgrading an Optimizely CMS solution to .NET 10, we came across an issue where the Language Manager gadget completely disappeared...

Madhu | Aug 2, 2026 |

Flat or Nested? Weighing Your Content Modeling Options in Optimizely SaaS CMS

When building a headless site on Optimizely SaaS CMS, one of the earliest and most critical design milestones your team will face is defining your...

Vipin Banka | Jul 31, 2026

From SDK to Core: Modernizing Optimizely Configured Commerce for .NET 8 and .NET 10

The .NET Framework 4.8 clock is running out for Configured Commerce customizations. Handled well, this deadline is not a chore it is the cleanest...

Vaibhav | Jul 29, 2026