Views: 2132
Number of votes: 3
Average rating:

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

Vincent
(By Vincent, 3/22/2016 5:40:18 AM)

Good to know :)

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


Henrik Fransas
(By Henrik Fransas, 3/22/2016 8:57:45 AM)

That is true!

Missed to inform about that. Thanks!

Jonas  Carlbaum
(By Jonas Carlbaum, 10/22/2018 10:57:05 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.

Please login to comment.