Wcf – “The current configuration system does not support user-scoped settings”

asp.netwcf

We're getting a "The current configuration system does not support user-scoped settings" compilation exception being thrown when navigating to a WCF service on our staging server.

We're getting this exception through the app consuming the WCF service and when we navigate to the .svc test page directly.

This works fine on our test servers – and the websites are setup in the same way (in IIS, in the filesystem etc. etc.).

Does anybody have an idea of what this would be?

Best Solution

My problem was simple, check in the project's Settings.setting page/file to see if the Scope column is set to User instead of Application:

enter image description here

Related Solutions

R – Benefits & pitfalls of moving to IIS 7, Windows Server 2008 for WCF Services

As you mentioned, IIS 6 only has support for the various HTTP-based bindings. IIS7 has support for all the bindings, including TCP/IP, named pipes (for superfast in-proc calls on the same machine), and MSMQ queue.

For a detailed comparison between hosting WCF in IIS6 and IIS7, see this MSDN article: Extend Your WCF Services Beyond HTTP With WAS

.net – WCF service startup error “This collection already contains an address with scheme http”

In .Net 4, you can use the multipleSiteBindingsEnabled option:

<system.serviceModel>
    <serviceHostingEnvironment multipleSiteBindingsEnabled="true">
    </serviceHostingEnvironment>
</system.serviceModel>

Then, you won't have to specify each address.

http://msdn.microsoft.com/en-us/library/system.servicemodel.servicehostingenvironment.multiplesitebindingsenabled.aspx

Best Solution

Related Solutions

R – Benefits & pitfalls of moving to IIS 7, Windows Server 2008 for WCF Services

.net – WCF service startup error “This collection already contains an address with scheme http”

Related Question