I use the "configSource" property on parts of my web.config file, so that I can have one master web.config file which is the same for all customers, and then parts which vary between customers (e.g. globalization settings) are isolated into separate files:
When I install or update Westwind Globalization with NuGet, it edits my web.config (which I accept is normally a helpful thing to do) and adds the resourceProviderFactoryType="Westwind.Globalization.DbSimpleResourceProviderFactory,Westwind.Globalization.Web" setting to the globalization tag so it looks like this:
which is not allowed and causes it to throw an error. (There's a similar problem with the DbResourceConfigration section).
The installer should check for the presence of a configSource property, and if it exists, update the targeted config file instead of breaking web.config.
I use the "configSource" property on parts of my web.config file, so that I can have one master web.config file which is the same for all customers, and then parts which vary between customers (e.g. globalization settings) are isolated into separate files:
When I install or update Westwind Globalization with NuGet, it edits my web.config (which I accept is normally a helpful thing to do) and adds the resourceProviderFactoryType="Westwind.Globalization.DbSimpleResourceProviderFactory,Westwind.Globalization.Web" setting to the globalization tag so it looks like this:
which is not allowed and causes it to throw an error. (There's a similar problem with the DbResourceConfigration section).
The installer should check for the presence of a configSource property, and if it exists, update the targeted config file instead of breaking web.config.