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

WiX v4 decompile-to-product doesn't schedule actions #5898

Closed
barnson opened this Issue Nov 7, 2018 · 1 comment

Comments

Projects
None yet
1 participant
@barnson
Copy link
Member

barnson commented Nov 7, 2018

  • Which version of WiX are you building with?

package id="WixToolset.MSBuild" version="4.0.0-build-0027"

  • Which version of Visual Studio are you building with (if any)?

n/a

  • Which version of the WiX Toolset Visual Studio Extension are you building with (if any)?

n/a

  • Which version of .NET are you building with?

4.7.2

  • If the problem occurs when installing your packages built with WiX, what is the version of Windows the package is running on?

n/a

  • Describe the problem and the steps to reproduce it.

When you set the decompiler context's DecompileType = OutputType.Product, actions aren't scheduled. (i.e., no InstallExecuteSequence and friend elements are emitted.)

  • Describe the behavior you expected and how it differed from the actual behavior.

Actions should be scheduled, as they are when decompiling to module source.

@barnson barnson self-assigned this Nov 8, 2018

@barnson barnson added this to the v4.0 milestone Nov 8, 2018

@barnson

This comment has been minimized.

Copy link
Member

barnson commented Nov 14, 2018

DecompileType = OutputType.Product for a merge module doesn't schedule actions because the decompiler doesn't bother looking for the Module* tables. However, if you set TreatProductAsModule to true, it does. Not sure if this is a real bug. Please do that triage thing, triage team!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment