Hello, Sergei!

Not sure about Votive and output files.

But since WiX is based on XML, you can add post-build action to your ASP.NET
project that will generate XML file,
where all the files that need to be installed will be defined.

--
With best regards, Vadym Stetsiak.
Blog: http://vadmyst.blogspot.com

You wrote  on Thu, 13 Sep 2007 14:13:38 -0700:

SS> Hi.
SS> I wonder if there's something similar to "Project output" concept
SS> for
SS> Wix setup projects created using Votive.

SS> We are currently using Web setup project followed by  Custom Action
SS> that is used to do most of the work to deploy a big ASP.NET
SS> application.
SS> We are considering moving the deployment to either WiX or a
SS> completely custom tool because of the utter lack of functionality in
SS> Web Setup projects.

SS> The problem is that the project has hundreds of files in a
SS> complicated subdirectory tree in several separate projects and files
SS> are constantly added, removed and moved around from version to
SS> version.
SS>  Web setup has the advantage of packaging all the required files
SS> easily, I wonder if this is available for WiX.

SS> Application is basically a monolithic entity and the update includes
SS> the removal of most files (apart from maybe 3-5 files and 1-2
SS> subdirectories) and redeployment of the new ones so we don't care
SS> about component versioning problems.