Last post Apr 25, 2018 04:42 PM by PatriceSc
Apr 22, 2018 01:53 AM|danderson___|LINK
We are migrating a very large ASP application to ASP.NET MVC 5. Hopefully shortly after to core. Our situation is that our application is installed on premise at each clients location on a server, due to security. We have never shipped a web.config with
our software before, most settings were added manually over time. Each of them do have web.config files configured to set things like appSettings, httpRuntime.maxRequestLength, et cetera. Our customer's do
their own updates and upgrades, but don't have a clue what a web.config is, and would not expect to be responsible for modifying one. Over the years we have typically made these changes as needed. Upgrades are deployed via our custom Upgrade executable, which
is a wizard style WPF app.
Now, we have binding redirects, EF settings, want to migrate the connection string to the web.config, and provide our MVC settings like webpages:Enabled value = false, but how do we support this scenario?
webpages:Enabled value = false
I have looked at using file= and configSource= for certain sections, but not all elements support that (e.g. runtime), and it is very limited. It doesn't seem there is the capability
to have two web.config files in the same directory that support inheritance (such as web.default.config, web.customer.config).
but there are still other settings that are not supported from code, like webPages:Enabled.
Are we going to be forced to make our clients redo their web.config files? What do we do when we need to deploy updates to this file, such as additional binding redirects? Every client may be different as well, such as enabling Windows authentication or
From what I have read in most scenarios, the consensus is deploy the web.config manually and make the changes, but in these cases they have control over the hosting environment and its usually a single production server. We're talking about 150+ unique installations
in our case, across 150+ unique customers.
Apr 25, 2018 04:42 PM|PatriceSc|LINK
Not sure about how web.config transformations are handled and if is exposed for external consumption or maybe some 3rd party tool. And so you would write something like
https://msdn.microsoft.com/en-us/library/dd465326(v=vs.110).aspx to describe which changes are absolutely required and the upgrade wizard would then, update the config file accordingly
? Just thinking aloud here...
Edit: I found https://github.com/erichexter/WebConfigTransformRunner (based apparently on a transformation engine released by the ASP.NET team)