Quote Originally Posted by chris128 View Post
Yeah if the user already installed it to a custom path it will pick up on that and use that if its an upgrade for an existing installed program.

As for updating the registry and Add/Remove Programs, its actually not that hard to do that yourself (see my post here to see where add/remove programs pulls this from in the registry) but I would recommend doing it the "proper" way with an MSI as you are planning to do
After playing with it for a while I've noticed that out of the box, it does not pick up a previously installed path. What it ends up doing is giving the user the option to change the path, but the value filled in is the default, and if you click next right through what ends up happening is it'll uninstall the previous version (I have this turned on, I know) then it installs the new version in the default location instead. After doing some reading it may be possible to use Orca to modify the msi file after it's been built to get it to pick up the previously installed path, but that's more work for each release & I haven't gotten it to work yet anyways.
What I'm doing now is I remove the destination path dialog from the UI sequence in VS, so the app will only be installed in the default location (user's program files folder) and all subsequent installs will be in the same location. Plus it's one less "next" for the users to click without paying attention anyways.