This is enforced by .NET itself. We have a custom configuration section, it does not let you append or change it in any way, however, this is easy. You either have no config file and use our configless support our use the config file for both connections.

You can easily have two connections (or 50) in the ES config area, or just add them all in code. You need to remove both sections from your config file to get rid of this error. 

FYI: Config sections can be read multiple times, not just when the program loads, and as pointed out, you can create multiple connections within a section.

I do not recommend hard-coding the connections. If you do and you need to make a change, you then must recompile the library and redistribute the .dll. With a config section, the changes can be made and the settings will auto-change upon reloading the application. You can also create routines in your code to force a reload of configuration settings while the application is running. I am not sure about a reloading web config section in ASP .NET, but nothing says you have to use web config. If you read up on .NET configuration sections, you can create you own. Further, .NET supports encrypting config sections too.

I got the same error.  What I don't think is clear is that you have to remove all references to entity spaces in a config file - both

     <EntitySpaces>
        <connectionInfo default="SQL">
            <connections>
                <add name="SQL" providerMetadataKey="esDefault" sqlAccessType="DynamicSQL" provider="EntitySpaces.SqlClientProvider" providerClass="DataProvider"
                        connectionString="server=dqsqls0140s.devfbr.com\dev;database=EPM;Integrated Security=true" databaseVersion="2000" />
            </connections>
        </connectionInfo>
    </EntitySpaces>

 and

        <sectionGroup name="EntitySpaces" type="EntitySpaces.Interfaces.esConfigSettings, EntitySpaces.Core">
            <section name="connectionInfo" type="EntitySpaces.Interfaces.esConfigSettings, EntitySpaces.Interfaces" allowLocation="true" allowDefinition="Everywhere" restartOnExternalChanges="true"/>
        </sectionGroup>

 Then using the config-less option you will be fine.
 

Sorry. It can be hard for us to look at things with fresh eyes. We sometimes assume things because they are so familiar to us. Currently, under "Configless Execution" in the "Getting Started" PDF, we have:

"You must remove all EntitySpaces sections from the app/web .config file to use configless execution. You cannot use both."

We are open to suggestions. Would this re-wording make things clearer?

"You must remove all EntitySpaces configuration elements from the app/web .config file to use configless execution. Delete the "EntitySpaces" <configSections> entry, and the entire <EntitySpaces>...</EntitySpaces> section. You may still use a config file with EntitySpaces in configless mode. But, it cannot contain any EntitySpaces entries, only the other sections required by your application."