Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 88199
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 10, 20262026-05-10T22:31:20+00:00 2026-05-10T22:31:20+00:00

Update: looks like this is indeed a WiX limitation – Cannot add 64bit com+

  • 0

Update: looks like this is indeed a WiX limitation – Cannot add 64bit com+ component (3.0.3907.0)

I have a .NET application with an MSI installer created using WiX 2.0. The installer creates a COM+ application (amongst other things) and installs a .NET assembly as a component into this application. This DLL is pure managed, however it calls into a mixed DLL which may be 32-bit or 64-bit. On a 32-bit platform everything works fine. On 64-bit however, the COM+ dllhost.exe process runs as 32-bit and subsequently fails to load the native DLL. When I look in the registry I can see that the COM+ component DLL has been registered under the Wow6432Node key and I presume that’s why dllhost is running as 32-bit.

If I use the Component Services snap-in to remove and re-add the DLL it all gets registered properly in the ‘real’ registry and dllhost starts as 64-bit. How do I get the installer to do the same, ie. register it properly as a 64-bit DLL? I’ve already set the Package Platform attribute to ‘x64′ and set the Win64=’yes’ attribute for every Component, but these didn’t seem to help.

The WiX source for the COM+ component looks like this:

      <Component Id='C_My.Server.dll_ComPlus' Guid='0117c6c5-387a-4b67-9a7f-273d5db3affd' Win64='yes'>         <File Id='F_My.Server.dll_ComPlus' Name='SERVER.DLL' LongName='My.Server.dll' Vital='yes' KeyPath='yes'               Assembly='no' DiskId='1' Source='..\Server\bin\$(var.Configuration)\' />         <pca:ComPlusApplication Id='MyServerComPlusApp' Name='My Server' RunForever='yes'           ApplicationDirectory='[INSTALLDIR]ComPlusConfig' ApplicationAccessChecksEnabled='no'           Identity='[ComPlusUserName]' Password='[ComPlusPassword]'>           <pca:ComPlusAssembly Id='MyServerComPlusAssembly' DllPath='[#F_My.Server.dll_ComPlus]'             TlbPath='[#F_My.Server.tlb_ComPlus]' Type='.net' RegisterInCommit='yes'>             <pca:ComPlusComponent Id='CheckInterface' CLSID='d4cf3da5-83ad-4436-b174-eccdb121a9ea' />           </pca:ComPlusAssembly>         </pca:ComPlusApplication>       </Component> 
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. 2026-05-10T22:31:20+00:00Added an answer on May 10, 2026 at 10:31 pm

    More likely than not this is a deficiency in the COM+ CustomAction. It probably only supports 32-bit code right now.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have an Ajax Form that looks like this: <% using (Ajax.BeginForm(Update, new AjaxOptions
I have a system setup like this: http://joemaller.com/990/a-web-focused-git-workflow/ However no matter how I configure
Update : Looks like the query does not throw any timeout. The connection is
I'm trying to make something that looks like this, but I don't know how
I've got a form that looks like this: <form method=post> {% csrf_token %} <table>
Update: Check out this follow-up question: Gem Update on Windows - is it broken?
UPDATE: Focus your answers on hardware solutions please. What hardware/tools/add-in are you using to
Update: Now that it's 2016 I'd use PowerShell for this unless there's a really
I have this C# webform that has has a date picker box. If the
This behavior is making me wonder about my sanity.. I have a form that

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.