Hi David
I've been working on the Visual Studio Harvester for quite some time now
(not officially anyway) and I also wish to submit my changes to the WiX
source base.
I don't think it will happen for WiX 3.8 but from 4.0 it should take track,
I think.
What you could do in the mean time is follow the discussion that the guys
are having with compiling the Wix 3.8 source base as this will become the
new foundation on which 4.0 will run.
To look at the Heat project (or more precisely the VS Harvester), have a
look at the "ext" folder in the WiX source base.
I don't know how the new compilation process is but previously (in WiX 3.5)
I had to pull that project out and compile standalone in order to know that
the stuff I've been working on actually works. I then just merged the
changes back into the main source base.
I'm currently refactoring the VS Harvester and then I want to apply some
changes that will cause the harvester to load not just the current project
but all its dependencies as well.
Best of luck
Regards,
Dandre
On Wed, Mar 27, 2013 at 6:11 PM, David G. van Hoose <
david.g.vanho...@gmail.com> wrote:
> Hello everyone,
>
> I have recently started using WiX on Visual Studio 2010 due to the removal
> of the Visual Studio Deployment Projects in Visual Studio 2012. I love the
> power of WiX, but there are some places where I am experiencing some
> issues. One of these issues is with transparent Heat automation through
> Visual Studio.
>
> The first problem that have faced is that the aggregate values for Project
> Output Groups does not cover the scenarios that I use. I am very much
> biased against the use of aggregate values. I prefer straight Boolean
> values that can be used for a generative command-line. The harvesting also
> seems to ignore the Project Output Groups anyway, and this is causing Heat
> to fail. I would like to approach both of these issues together. The
> problem that I am faced with, is where to begin. I downloaded the source
> code, but I could only find processing code for the Project Output Groups.
> I could not find the coding for the Visual Studio property. I looked in the
> Votive 2010 code, but could not find anything there. Can anyone tell me
> where I should be looking? Does anyone have any thoughts to add?
>
> The second problem is with the regeneration of component GUIDs each time
> Heat harvests a project. I have read that generating new component GUIDs
> with patch releases causes all of the components to be reinstalled as new,
> even if they were not updated. My goal here would be to have Heat be able
> to update existing harvested files and keep a history of the GUIDs. Does
> this goal have merit or is the premise baseless? Is there a better way?
>
> Best Regards,
> David
>
>
>
> ------------------------------------------------------------------------------
> Own the Future-Intel® Level Up Game Demo Contest 2013
> Rise to greatness in Intel's independent game demo contest.
> Compete for recognition, cash, and the chance to get your game
> on Steam. $5K grand prize plus 10 genre and skill prizes.
> Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d
> _______________________________________________
> WiX-devs mailing list
> WiX-devs@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-devs
>
>
------------------------------------------------------------------------------
Own the Future-Intel® Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest.
Compete for recognition, cash, and the chance to get your game
on Steam. $5K grand prize plus 10 genre and skill prizes.
Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
