ClickOnce deployed application
The application uses a different set of user configuration data (settings) when launched through a registered file extension (double-click on the file) than it does when launched normally through the launch icon created by the ClickOnce installation.
Searching for the user.config file on the system, I see that 2 different files are created.
When the application is launched from a standard icon, user.config is in the C:\Users\Jacques\AppData\Local\JBFI\JBFlow.exe_StrongName... directory, JBFI being the name of the company provided in the ClickOnce deployment setup, and JBFlow.exe the name of the application.
When the application is launched through the file association, it ends up in C:\Users\Jacques\AppData\Local\Apps\2.0\Data\<standard ClickOnce garbage>\jbfl..tion..... directory.
Same user, but 2 sets of configuration settings.
Did somebody encountered that problem and found a way to have the same set of settings for the 2 different ways of launching the application?