I do not have direct experience with this, but from studying the source code
for another purpose, I think you need to do something like:
<Fragment>
<ComponentGroup Id="ProductComponents" Directory="INSTALLFOLDER">
<Component Id="ProductComponent">
<File Id="VSIXProject.vsix" KeyPAth='yes' Source="path to
the file" />
<VSExtension:VsixPackage File="VSIXProject.vsix"
PackageId="VISXProject" />
</Component>
</ComponentGroup>
</Fragment>
or something like this:
<Fragment>
<ComponentGroup Id="ProductComponents" Directory="INSTALLFOLDER">
<Component Id="ProductComponent">
<File Id="VSIXProject.vsix" KeyPAth='yes' Source="path to
the file">
<VSExtension:VsixPackage PackageId="VISXProject" />
</File>
</Component>
</ComponentGroup>
</Fragment>
I hope this is helpful and I apologize if I am presumptuous, not having
directly tried this.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Does-anyone-have-a-VSIX-example-tp7580711p7590624.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
