You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following registry key:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{A CONSTANT VALUE}
What did you see instead?
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall{A value that changes}
Useful extra information
We have an app that has a shortcut to launch DB Browser with certain command line parameters. IT would be nice to be able to query the registry to find the install location.
The GUID is the product code, so I assume should be consistent. I assume if its not provided in the setup, the MSI will randomly create one.
This would be more for internal use though. To get the install location, this could be stored in the DB4S settings, or even Computer\HKEY_CLASSES_ROOT\Applications\DB Browser for SQLite.exe\shell\open\command ... although that isn't 'clean'.
The second registry key (with WOW6432Node) means you have a 32-bit installation on a 64-bit Windows. You should find the first key on a 32-bit Windows, or on a 64-bit Windows with 64-bit installation.
Either way, Chris is right and these values you use are GUIDs and for internal use and you shouldn't depend on.
IT would be nice to be able to query the registry to find the install location.
You are right. This was an oversight on my part. I should have done it earlier. I just added an InstallLocation (seems to be a standard name) to HKEY_LOCAL_MACHINE\SOFTWARE\DB Browser for SQLite key.
@chrisjlocke - For most apps, the product GUIDs are constant and do not change between releases but that does not seem to be the case for DB Browser though.
Activity
justinclift commentedon Jul 12, 2020
@karim @chrisjlocke Any ideas?
chrisjlocke commentedon Jul 12, 2020
The GUID is the product code, so I assume should be consistent. I assume if its not provided in the setup, the MSI will randomly create one.
This would be more for internal use though. To get the install location, this could be stored in the DB4S settings, or even Computer\HKEY_CLASSES_ROOT\Applications\DB Browser for SQLite.exe\shell\open\command ... although that isn't 'clean'.
Save the install location to Windows Registry
karim commentedon Jul 12, 2020
The second registry key (with
WOW6432Node) means you have a 32-bit installation on a 64-bit Windows. You should find the first key on a 32-bit Windows, or on a 64-bit Windows with 64-bit installation.Either way, Chris is right and these values you use are GUIDs and for internal use and you shouldn't depend on.
You are right. This was an oversight on my part. I should have done it earlier. I just added an
InstallLocation(seems to be a standard name) toHKEY_LOCAL_MACHINE\SOFTWARE\DB Browser for SQLitekey.justinclift commentedon Jul 12, 2020
@karim Oh, that's cool. We'll add that to the hopefully-somewhat-soon 3.12.1 release. 😄
TonyValenti commentedon Jul 12, 2020
@chrisjlocke - For most apps, the product GUIDs are constant and do not change between releases but that does not seem to be the case for DB Browser though.
Save the install location to Windows Registry