Rafuse Robert wrote:
> I'm not using merge modules for this sample... the wxs file in the OP is the
> sole source I'm using.  However... I searched through the source of my
> earlier attempts at this and the very first one had a custom action
> Assign_TARGETDIR... I'd forgotten I'd done that, sorry.  But this was in a
> differently named .wxs file in another folder, so I'm not sure why this info
> was getting bound into my .msi... yet not showing up in ORCA.  I was
> definitely not referencing the older wxs file...  I assume it has something
> to do with the fact that I had not changed the GUID on the Product since I
> started futzing around with this sample last weekend.  
In an earlier message, you showed a hard-coded Package/@Id attribute. 
You should always use the question-mark method of specifying the package 
code -- MSI rules say that every package should have a different package 
ID. Likely, you still have an older version of the .msi installed, so 
MSI is running the original package.
> DEBUG: Error 2723:  Custom action Assign_C_ROOT specifies unsupported type
>   
Can you post the .wxs file that produced this error? It looks like a WiX 
bug that it let you create an invalid CA type.

-- 
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

Reply via email to