Skip to content
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

Support Windows Server Core without WoW64 support #4826

Closed
wixbot opened this issue Jul 15, 2015 · 11 comments
Closed

Support Windows Server Core without WoW64 support #4826

wixbot opened this issue Jul 15, 2015 · 11 comments
Assignees
Milestone

Comments

@wixbot
Copy link

wixbot commented Jul 15, 2015

It looks like the WiX extensions fail on executing when the target system does not include the WoW64 support.

Invoking remote custom action. DLL: C:\Windows\Installer\MSI5B3C.tmp, Entrypoint: ConfigureIIs
MSI (s) (94:34) [08:33:46:793]: Generating random cookie.
MSI (s) (94:34) [08:33:46:793]: Failed to create Custom Action Server. Error 308.

Can you change that so it can be running without WOW64 installed? Thanks TomasK

Originally opened by tomask

@wixbot
Copy link
Author

wixbot commented Jul 21, 2015

Could do custom actions only in v3.x; the Burn change is v4 only, because we currently swap in the x86 burn stub.

Release changed from v3.8 to v4.0

@wixbot
Copy link
Author

wixbot commented Jul 22, 2015

Type changed from Bug to Feature

@rseanhall
Copy link
Contributor

I guess we're using this issue for ARM/ARM64 Custom Actions as well as pure x64 Custom Actions. ARM/ARM64 custom actions are already in v3.14. x64 Burn is tracked at #4579.

@barnson
Copy link
Member

barnson commented Mar 7, 2021

Custom actions are implemented. x64 Burn is tracked at #4579.

@barnson barnson closed this as completed Mar 7, 2021
@rseanhall
Copy link
Contributor

@barnson Dependency.wixext only has x86. I didn't check all of them, so maybe others as well.

@barnson
Copy link
Member

barnson commented Mar 7, 2021

@rseanhall [citation needed] I see all three platforms in the compiler extension, CA, and wixlib.

@rseanhall
Copy link
Contributor

I was looking at the .sln, which I guess doesn't matter. https://github.com/wixtoolset/Dependency.wixext/blob/master/Dependency.wixext.sln

@barnson
Copy link
Member

barnson commented Mar 7, 2021

And appveyor.cmd only builds the extension DLL, which is a little weird compared to other projects, but the project references mean it all works.

@rseanhall
Copy link
Contributor

@barnson Fine. You made me look. VisualStudio, Msmq, DirectX all x86 only. COM+ only x86/x64. UI looks almost correct, but wixlib project is only referencing the CA project once so not sure how that's working. DifxApp also not building the CA in the wixlib project.

@barnson
Copy link
Member

barnson commented Mar 7, 2021

VisualStudio is explicitly correct because VS itself is x86-only. When it goes x64/ARM64, I'll worry. UI is problematic because the CAs are implicitly referenced; it really needs a compiler extension so we can control the CA references. DifxApp is special because we don't own/build the CAs, so they have to be added explicitly via the .wixlibs. The rest are legit, albeit boring.

@barnson barnson reopened this Mar 7, 2021
@barnson barnson added this to To do in wix.4.0-preview.1 via automation Jul 8, 2021
@barnson
Copy link
Member

barnson commented Oct 24, 2021

Tracking todos in #5933.

@barnson barnson closed this as completed Oct 24, 2021
wix.4.0-preview.1 automation moved this from To do to Done Oct 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

No branches or pull requests

3 participants