Hi Sergie,
I'm just starting out on WiX as well so take what I say with a pinch
of salt but ... You can use tallow
(http://www.tramontana.co.hu/wix/lesson5.php#5.2) However IMHO it's
not pretty as you have to do a fair bit of manual fixing.
I was surprised that this was missing as well and asked if there were
any plans / requirements docs etc. for writing/completing tallow but
didn't get a response when I posted to the wix-users
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg11554.html
I'm in the process of writing an ant task so I can use it to generate
fragements from dir sets ... I'm literally writing it as we speak so
far it's following the pattern below
<tallow guidCommand="guidgen.exe" dir="." componentGroup="Core"
fragmentFileName="Core_frag.wxa" fragmentRoot="INSTALLDIR">
<!-- specify files under the same directory hierarchies -->
<!-- j15 mapped to jre15 -->
<dirGroup dir="${stage.dir}/j15" prefix="jre15">
<resourceSet location="${stage.dir}/j15">
<fileset dir="${stage.dir}/j15" casesensitive="yes">
<include name="**/*"/>
</fileset>
</resourceSet>
</dirGroup>
...
</tallow>
Idea being that you create you fragment Core_fraq.wxa by listing
<dirGroup> and specifying the files you need. The result should be a
component group called Core which contains refs to all the Components
specified in the dirGroup elements. One component per directory.
kind regards,
Kaveh.
Sergei Shelukhin wrote:
> Hi.
> I wonder if there's something similar to "Project output" concept for
> Wix setup projects created using Votive.
>
> We are currently using Web setup project followed by Custom Action that
> is used to do most of the work to deploy a big ASP.NET <http://ASP.NET>
> application. We are considering moving the deployment to either WiX or a
> completely custom tool because of the utter lack of functionality in Web
> Setup projects.
>
> The problem is that the project has hundreds of files in a complicated
> subdirectory tree in several separate projects and files are constantly
> added, removed and moved around from version to version. Web setup has
> the advantage of packaging all the required files easily, I wonder if
> this is available for WiX.
>
> Application is basically a monolithic entity and the update includes the
> removal of most files (apart from maybe 3-5 files and 1-2
> subdirectories) and redeployment of the new ones so we don't care about
> component versioning problems.
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
