In Visual Studio 2008, I was using MFC’s registry calls to save my program preferences. \u00a0The problem was new builds weren’t using the prior build’s settings. I was adding the build number to the .exe<\/tt> filename and this caused a new key to be created in the registry based on the .exe<\/tt> name and a new set of settings saved therein. \u00a0Inspecting CWinApp<\/tt>‘s\u00a0m_pszAppName<\/tt>\u00a0and\u00a0m_pszExeName<\/tt>\u00a0I saw both were\u00a0PuffinApp914<\/tt>. \u00a0It turns out\u00a0m_pszAppName<\/tt> is set to the string resource ID AFX_IDS_APP_TITLE<\/tt> if it’s there. \u00a0If AFX_IDS_APP_TITLE<\/tt> doesn’t exist then m_pszAppName<\/tt> is set to the .exe<\/tt> filename. \u00a0After adding\u00a0AFX_IDS_APP_TITLE<\/tt>\u00a0to the project’s string resources\u00a0m_pszAppName<\/tt> became Puffin<\/tt> and\u00a0m_pszExeName<\/tt> stayed with\u00a0PuffinApp914<\/tt>. \u00a0The registry calls use\u00a0m_pszAppName<\/tt>\u00a0for the key so my problem was solved.<\/p>\n","protected":false},"excerpt":{"rendered":"
In Visual Studio 2008, I was using MFC’s registry calls to save my program preferences. \u00a0The problem was new builds weren’t using the prior build’s settings. I was adding the build number to the .exe filename and this caused a new key to be created in the registry based on the .exe name and a … Continue reading Preventing Renamed App From Creating New Registry Entry<\/span>