I'm adding an MSI file to an application normally deployed to the servers as a One-Click deployment. We have numerous configuration transforms for the app.config and I just changed the existing one to merge production servers into the app section.
Normal (unmerged setting -- default to localhost for services):
<appSettings file="c:\config\SERVPRO.WorkCenter.FranchiseClient.user.config">
<add key="placeholder" value="SoThisWillNotGoAway" />
<add key="ClientSettingsProvider.ServiceUri" value="" />
</appSettings>
The merged version for release:
<appSettings xdt:Transform="Replace">
<add key="DataServerHostName" value="prduction server naem"/>
<add key="AuthenticationServerHostName" value="production server name"/>
<add key="DataServerPortNumber" value="666"/>
<add key="AuthenticationServerPortNumber" value="666"/>
<add key="DisplayLocationInformation" value="True"/>
<add key="Location" value="Production"/>
</appSettings>
Now I have gone in and verified that a) the msi construction does grab the app config file --and-- b) the app config contains the release data for the production servers.
When I install the application and inspect the files I get the non-merged version of app.config in the installed files instead of the output from the build of the application!!! If gone in and deleted all instances of the build except release and I still get this.
Does the MSI creation construct the app.config => program.exe.config itself and overlooks the transforms??? If so am I now required to tell it manually to get the correct file from the Release folder, rather than use the project output?
Any help is greatly appreciated. I've not found anything on this in my googling.