The only way I could think you could do this is add a post-update exe or batch file that encrypts the settings immediately after the update has been processed.
Hi,
I am in the middle of implementing encrypted connection strings and application settings in app.config for some of my applications. I have code that uses .Net's built in protection libraries (ConfigurationManager.Section.Protect()) when the application launches it checks if the section I'm concerned with are protected, and if not, it protects them. My installer also encrypts app.config for new installations during install.
The issue I am trying to work around, is every time I put out an update with wyBuild, app.config on the target machines gets overwritten with the non-encrypted version that the update package has and then it has to be re-encrypted next time the application is launched. Now, this isn't a huge issue, but it does leave the sections I want encrypted in plain text until the user actually starts the application.
Can you advise on how to work with this?
Thanks,Scott
The only way I could think you could do this is add a post-update exe or batch file that encrypts the settings immediately after the update has been processed.
Yeah, that's all I could come up with too.