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

Warn against using ServiceConfig and ServiceConfigFailureActions #5306

Closed
barnson opened this Issue May 24, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@barnson
Member

barnson commented May 24, 2016

Please provide answers to the following questions to help us narrow down, reproduce, and fix the problem. Fill out one section and delete the others.

Bugs

If this issue is a bug:

  • Which version of WiX are you building with?

n/a

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

n/a

  • Which version of .NET are you building with?

n/a

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

Windows 7 and later

  • Describe the problem and the steps to reproduce it.

The MsiConfigureServices doc warns against using the feature because "this functionality is not working as expected."(!)

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

Well, I'd expect engine features to, you know, work as expected, but failing that, the WiX doc should warn against using them. Maybe make it a compiler warning?

@barnson barnson added this to the v3.11 milestone Jun 7, 2016

@barnson barnson self-assigned this Jun 7, 2016

@BMurri

This comment has been minimized.

Collaborator

BMurri commented Jul 14, 2016

The pull requests in wix3 and wix4 purported to resolve this appear to both be closed after having been applied to their respective develop branches. Shouldn't the bug be closed, too?

@barnson

This comment has been minimized.

Member

barnson commented Jul 18, 2016

Yep.

@barnson barnson closed this Jul 18, 2016

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