On 4/8/2010 5:27 PM, Neil Sleightholm wrote:
> But there wouldn't be any project references as they are external
> assemblies.
>
OK. Feel free to file the bug; there are others in the triage team that
are more sympathetic to harvesting.
--
sig://boB
http://joyofsetup.com/
But there wouldn't be any project references as they are external
assemblies.
Neil
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: 08 April 2010 22:08
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] how to use heat to harvest VS projects
On 4/8
On 4/8/2010 4:54 PM, Neil Sleightholm wrote:
> Afraid not, "Content" just includes icons, images etc (mainly useful for
> web apps). I have checked this with 3.0 and 3.5. I feel this is quite a
> big hole in the project harvester, is it worth a bug report?
>
You can try. I don't think it's a b
Sent: 08 April 2010 13:45
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] how to use heat to harvest VS projects
On 4/6/2010 5:23 PM, Neil Sleightholm wrote:
> I have checked this again and using heat with the options
"-pog:Binaries
> -pog:Satellites -pog:Content" the
On 4/6/2010 5:23 PM, Neil Sleightholm wrote:
> I have checked this again and using heat with the options "-pog:Binaries
> -pog:Satellites -pog:Content" the referenced assemblies are not
> included.
>
I thought they'd end up as "Content."
--
sig://boB
http://joyofsetup.com/
-
Sent: 01 April 2010 01:29
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] how to use heat to harvest VS projects
On 3/31/2010 8:41 AM, Neil Sleightholm wrote:
> Afraid not that only gets the primary output not referenced
assemblies.
>
Aren't they in the content output
ceforge.net
Subject: Re: [WiX-users] how to use heat to harvest VS projects
On 3/31/2010 8:41 AM, Neil Sleightholm wrote:
> Afraid not that only gets the primary output not referenced assemblies.
>
Aren't they in the content output group?
--
sig://boB
On 3/31/2010 8:41 AM, Neil Sleightholm wrote:
> Afraid not that only gets the primary output not referenced assemblies.
>
Aren't they in the content output group?
--
sig://boB
http://joyofsetup.com/
--
Download Int
Afraid not that only gets the primary output not referenced assemblies.
Neil
Neil Sleightholm
n...@x2systems.com
On 30 Mar 2010, at 01:20, "Bob Arnson" wrote:
> On 3/29/2010 3:56 PM, Neil Sleightholm wrote:
>> I am afraid that is how heat works, it only finds the primary
>> output and
>> no
I was using the -pog switch.
Thanks,
Bill
On Mon, Mar 29, 2010 at 7:07 PM, Bob Arnson wrote:
> On 3/29/2010 3:56 PM, Neil Sleightholm wrote:
> > I am afraid that is how heat works, it only finds the primary output and
> > no referenced assemblies. If you want the referenced assemblies then you
On 3/29/2010 3:56 PM, Neil Sleightholm wrote:
> I am afraid that is how heat works, it only finds the primary output and
> no referenced assemblies. If you want the referenced assemblies then you
> have to heat those projects or files independently.
>
Or use the -pog switch, right?
--
sig://
Heat will take EVERYTHING in the directory you specify. It should pick up on
the COM DLLs just fine.
Brian Rogers
"Intelligence removes complexity." - Me
http://blogs.msdn.com/icumove
On Mon, Mar 29, 2010 at 1:20 PM, Bill McCormick (LIST) <
wpmccorm...@ace-co.com> wrote:
> Neil. Thanks so much
Neil. Thanks so much for the reply. I was beginning to think that maybe
I need to change body soap 'cause no one wanted to talk to me :'(
Will heat do the right thing if I just use the dir switch on a directory
that contains all the files that I want to install? Some may be COM (DLL
or OCX).
T
I am afraid that is how heat works, it only finds the primary output and
no referenced assemblies. If you want the referenced assemblies then you
have to heat those projects or files independently.
Personally I think this is major limitation of heat and makes the new
Harvest feature in WiX v3.5's
14 matches
Mail list logo
