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
Minor upgrade doesn't change files if EnableFeatureSelection="yes" in MsiPackage. #4616
Comments
When EnableFeatureSelection="yes" Burn calls back and you need to specify feature action states. If you're doing that, please reopen the bug and post the Burn log with details.
|
|
Log files: Msi log file: Removing old burn log file:
|
Please post your OnPlanMsiFeature code. |
STDMETHODIMP_(int) OnPlanMsiFeature(__in_z LPCWSTR wzPackageId, __in_z LPCWSTR wzFeatureId, __inout BOOTSTRAPPER_FEATURE_STATE* pRequestedState)
And in burn log you can see feature state (_pRequestedState) at exit from method.
|
Is this bug going to be fixed soon? |
This issue is open and unassigned. That means it is waiting for someone to investigate the root problem, discuss possible solutions to that problem then implement the decided solution. If you are interested in doing so yourself, our developer documentation provides a great checklist for getting started. If you are not interested then you are waiting for someone else to become interested. If this issue has been open for a long time then there probably isn't much interest in this particular issue. In that case, you'll want to consider how to motivate others to fix it for you. This is a pretty good list of support options. |
Minor upgrade doesn't change files if EnableFeatureSelection="yes" in MsiPackage.
We use own boostrapper applicationand and control features via OnPlanMsiFeature callback.Files will upgrade only if feature isn't presented in previous setup and is presented in new setup. All other files keep untouched.
I think it's because of when applying minor update REINSTALL property is empty, but must be REINTALL=ALL or REINTALL=<feature to reinstall 1>, ...
The text was updated successfully, but these errors were encountered: