SHGetKnownFolderPath appears to be the current official way of doing this: http://msdn.microsof...8(v=vs.85).aspx
If you're creating an installer I'd highly recommend that you use a well-known installer technology rather than trying to roll your own. Visual Studio, for example, can be used to create an MSI file, and it will resolve all of this for you, as well as provide for uninstallation (and also be compatible with remote deployment via e.g. Group Policy).
Show differencesHistory of post edits
#1mhagain
Posted 23 July 2012 - 08:37 PM
SHGetKnownFolderPath appears to be the current official way of doing this: http://msdn.microsoft.com/en-us/library/windows/desktop/bb762188%28v=vs.85%29.aspx
If you're creating an installer I'd highly recommend that you use a well-known installer technology rather than trying to roll your own. Visual Studio, for example, can be used to create an MSI file, and it will resolve all of this for you, as well as provide for uninstallation (as well as be compatible with remote deployment via e.g. Group Policy).
If you're creating an installer I'd highly recommend that you use a well-known installer technology rather than trying to roll your own. Visual Studio, for example, can be used to create an MSI file, and it will resolve all of this for you, as well as provide for uninstallation (as well as be compatible with remote deployment via e.g. Group Policy).