-
Notifications
You must be signed in to change notification settings - Fork 40
Uninstaller fails to remove file correctly with custom INSTALLDIR
#199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@stevapple ugh, that is really rather annoying. Would you be able to test this without the bootstrapper? That is, if you install to a custom location from the MSI does this happen? I suspect that this is happening in the bootstrapper, which is already problematic because it doesn't permit dual-purpose installers. |
It's actually the inverse. I did’t test with |
Oh, interesting. I wonder if it is due to the assignment because it isn't a standard directory. I think that at least partially this might be something that will be fixed due to shuffling of the toolchain location. |
The SDKs are still going to be an issue though ... |
I think that this is due to the following: <SetDirectory Id="WINDOWSVOLUME" Value="[WindowsVolume]" /> With the string of changes that are going in, I want to play a bit with the SDK, but I think that we can fix this. |
Fixed by #207 |
Looks like there's something wrong with the WiX configuration. Even if a custom
INSTALLDIR
was set on installation (and made into the database), the uninstaller will still reset it to default, making theRemoveFiles
step a no-op.The following is a derived piece from verbose MSI log:
The text was updated successfully, but these errors were encountered: