<section name=“couchbase” type=“Couchbase.Configuration.Client.Providers.CouchbaseClientSection, Couchbase”/>
But it needs to be:
<section name=“couchbase” type=“Couchbase.Configuration.Client.Providers.CouchbaseClientSection, Couchbase.NetClient”/>
Finding this information is pretty challenging, since the old client used to just find the configuration in the Web/App.config automagically.
This will be fixed in 2.1.0: https://issues.couchbase.com/browse/NCBC-853
Yeah, this was changed…in 1.X the “default” configuration was pulled from the .config file. In 2.x, the default constructor creates a “default” (localhost:8091) configuration so you can get up and running without having to create a configuration file. The thought was that it would be easier and less error prone for new developers to CB.
Thanks for the explanation.
While I agree that it’s easier for developers to get started (local was a no-brainer), it does expose some unexpected behaviors (at least in my dev environment), since I do test locally, I assumed my configuration worked, but when I migrate over to another environment, the alterations to the configuration don’t take effect (since they were otherwise incorrect and defaulted behavior took place), it did make the initial progression more difficult to diagnose.
Anyhow, I’ve got it, but I expect others to have this issue.