Thanks for your reply Bob ( do you ever sleep or just "live" on this list? :) ). I've done a bit more testing and have some empirical evidence of what the problem is. I went back to my simple.wxs testing and added a second COM+ assembly:
- Single "simple.wxs" file.
- First COM+ component contains children: File, Registry(s), ComPlusApplication, ComPlusAssembly, ComPlusComponent(s).
- Second COM+ component contains children: File, Registry(s), ComPlusAssembly (with added @Attribute=AppObj referring to earlier ComPlusApplication in first COM+ comonent), ComPlusComponent.
This revised simple test installs correctly, creates the COM+ application and adds both COM+ components - a total of 5 COM classes between the two DLLs. When I compare the "full-blown" msi to this new testing one I can see that the ComPlusApplication table is not being filled out correctly. It is missing the field/column "Component" -
a.k.a it's empty. On my simple.msi there is only one row in the ComPlusApplication table and it points to the first COM+ component (also where the ComPlusApplication tag was as indicated above).
I guess for now the work around is for me to manually merge my 14 individual wxs files (one per DLL - autogenerated) into the one "driver" BusinessObj.wxs that had just a ComPlusApplication child under the Fragment tag. According to the docs, as I said before, doing that seems to trigger "locator" behavior where it expects to find an existing COM+ application in the target install machine. If only there was a way (
e.g. @New=true) to trigger the creation behavior.
John
On 10/19/06, Bob Arnson <[EMAIL PROTECTED]> wrote:
John Watson wrote:"If the element is a child of any of the Fragment, Module or Product elements it is considered to be a locater, referencing an existing application. "Does this mean what I'm doing w/ the separate files can't be done? Is there a way to create (and probably correctly sequence) the creation of an empty COM+ application prior to the creation/registration of the components?
I know nothing about the COM+ CAs but I read that as saying that the "existing application" is one already present on the system, not being installed by the COM+ CAs in your package. If that's how it's designed, it makes sense that the extension wouldn't populate the ComPlusApplication table.
Can you put the ComPlusApplication element in its own component? As long as that component is installed along with the other components that contain the ComPlusComponent authoring, it should work, no?. Of course, remember what I said about knowing nothing about the COM+ CAs.<g>-- sig://boB http://bobs.org
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
