You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So with version 3.8 and 3.9 and Visual Studio 2013 I have found this no longer works. I was hoping 3.9 would resolve it. It isn't VS2013 in particular, I was wanting to build an installer with each component going forward. When I install I get error 1603 with the following information:
ComPlusInstallExecuteCommit: Error 0x80070490: Failed to get path for assembly from GAC
ComPlusInstallExecuteCommit: Error 0x80070490: Failed to register assembly, key: COMPONENTSERVICESTEST01ASSEMBLY
ComPlusInstallExecuteCommit: Error 0x80070490: Failed to register assemblies
CustomAction ComPlusInstallExecuteCommit returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
I have seen this issue raised on other forums over years and it appears that COM+ isn't used too much anymore but the same story occurs. It worked on v2.X of WiX and with version v3.5+ it doesn't with the same symptoms as others reported. The msi log entries are above. Responses as to why have included a design flaw in the installer where you can't put the dll in the application until it is register in GAC but those occur in the same step. I think problems with fusion have been blamed. Most constructive responses point to using custom actions. It doesn't appear to have been reported here. If it can be fixed that would be great. If anyone has any insight as to how I may have had it working before that would be great. Old machine was windows XP. New one is 64 bit Window 7. If it is something that I should pursue other solutions for because this won't be fixed I would like to know that as well.
Originally opened by jah
The text was updated successfully, but these errors were encountered:
I have an existing installer created on version 2.X of WiX that installs an application containing multiple COMPLUS applications that use a .NET DLL in GAC. All are installed together and basically follows the example in the tutorial on
http://wix.tramontana.co.hu/tutorial/com-expression-syntax-miscellanea/com-applications.
To create a package (My COM+ Application) and add a .Net assembly (MydotNet.dll) that is in the GAC to the package:
<complus:ComPlusApplication Id="MydotNet" Name="My COM+ Application">
<complus:ComPlusAssembly Id="MyComPlusAssembly" TlbPath="[#MydotNet_tlb]" Type=".net" DllPathFromGAC="yes" RegisterInCommit="yes">
<complus:ComPlusComponent Id="CheckInterface" CLSID="YOURCLSID-241E-4472-8C71-61A22BAF9914"/>
/complus:ComPlusAssembly
/complus:ComPlusApplication
So with version 3.8 and 3.9 and Visual Studio 2013 I have found this no longer works. I was hoping 3.9 would resolve it. It isn't VS2013 in particular, I was wanting to build an installer with each component going forward. When I install I get error 1603 with the following information:
MSI (s) (38:40) [20:55:42:762]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI7F81.tmp, Entrypoint: ComPlusInstallExecuteCommit
ComPlusInstallExecuteCommit: Error 0x80070490: Failed to get path for assembly from GAC
ComPlusInstallExecuteCommit: Error 0x80070490: Failed to register assembly, key: COMPONENTSERVICESTEST01ASSEMBLY
ComPlusInstallExecuteCommit: Error 0x80070490: Failed to register assemblies
CustomAction ComPlusInstallExecuteCommit returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
I have seen this issue raised on other forums over years and it appears that COM+ isn't used too much anymore but the same story occurs. It worked on v2.X of WiX and with version v3.5+ it doesn't with the same symptoms as others reported. The msi log entries are above. Responses as to why have included a design flaw in the installer where you can't put the dll in the application until it is register in GAC but those occur in the same step. I think problems with fusion have been blamed. Most constructive responses point to using custom actions. It doesn't appear to have been reported here. If it can be fixed that would be great. If anyone has any insight as to how I may have had it working before that would be great. Old machine was windows XP. New one is 64 bit Window 7. If it is something that I should pursue other solutions for because this won't be fixed I would like to know that as well.
The text was updated successfully, but these errors were encountered: