-
Notifications
You must be signed in to change notification settings - Fork 187
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
WindowsAuthProviderMergeModule #457
Comments
it's to be used part of an installer (wix or otherwise). I believe it installs the COM object interface, if I remember correctly, it was more of an experiment. I imagine there's about 0 users of this feature, so I would kill it, and open an issue with a reference in case someone cares to resurrect it. |
Thanks! Will do. |
I think I might leave this as is for now. Opening this back up. If I have the .net pieces gone, wix goes too. But then there is other setup. So since I don't fully understand how it's all working I'll leave as is for this upcoming release. |
IMO, I think those could all be extracted into a separate project. |
I'd agree now after getting it working. It's for an MSI so not much use on it's own. It wasn't being picked up in final build either. So now we have a working msm file in the final build but no real clue what to do with it. It's also working with nuget (entire .net) side even in visual studio. Wix did still require a separate install per Wix site in order to work in visual studio. So lots of pluses here but probably needs to go further ;) |
Related, #510 |
@dblock
How is this used? It is out of date on wix 3.7 and I've been building with 4.0. I'm very newbie with .net still so no clue how this is used. If I try to open the project in .net, it complains about the files in here as I don't have wix installed. I assume I need this in .net context and should be upgrading to match command line. Other option is to delete them but not sure what is right.
The text was updated successfully, but these errors were encountered: