Re: [WiX-users] Heat not replacing variable properly?

I have not used HarvestProject (or Heat.exe with a Project), but I use HarvestDirectory (which I prefer over calling heat.exe in a pre-build event), after calling a script which moves my project files to the directory. In this link

[WiX-users] Heat not replacing variable properly?

I am trying to get the files from a project using heat, with the following command in my prebuild: "$(WIX)bin\heat.exe" project "$(SolutionDir)Development\Armada\Armada.vbproj" -cg LoanProFiles -pog Binaries -pog Satellites -ag -g1 -dr INSTALLLOCATION -var env.LoanProFilesDir -out "$(ProjectDi

Re: [WiX-users] Heat source path

You could use a bind path (named or unnamed), which I have seen recommended over the use of preprocessor variables in this forum. Unnamed bind path: file source would be: wix.mybindname and then specify a XSLT transform some.xslt;..\..\Common\Transforms\bindpath.xslt which replaces the $(wix.mybin

Re: [WiX-users] Heat source path

Yes! I then got: 2015-04-17 12:20 GMT+02:00 Nir Bar : > Have you tried not specifying a variable to heat? > > > > - > Nir Bar > Freelance Developer > Mail: nir@panel-sw.com > Web: www.panel-sw.com >- C++ On Windows, Linux and Embedded Platforms >- WiX & InstallShield > -- > View

Re: [WiX-users] Heat source path

Have you tried not specifying a variable to heat? - Nir Bar Freelance Developer Mail: nir@panel-sw.com Web: www.panel-sw.com - C++ On Windows, Linux and Embedded Platforms - WiX & InstallShield -- View this message in context: http://windows-installer-xml-wix-toolset.687559.

[WiX-users] Heat source path

Hello, I use heat.exe to harvest a folder located outside the Msi-project. This is my current output in the generated wxs-file. In this case I need to set up var.ThePath in the project as pre processor variable (or use WiX-variable set up in the project). Is there any way I can directly give he

Re: [WiX-users] heat fragments go one directory too low

-srd Suppress harvesting the root directory as an element. http://wixtoolset.org/documentation/manual/v3/overview/heat.html -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-fragments-go-one-directory-too-low-tp7599560p7599571.html Sent fro

Re: [WiX-users] heat fragments go one directory too low

w.com] Sent: March-15-15 16:46 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] heat fragments go one directory too low Add -srd to the command line. -srd Suppress harvesting the root directory as an element. See the full doc for heat here: http://wixtoolset.org/documentation/m

Re: [WiX-users] heat fragments go one directory too low

Add -srd to the command line. -srd Suppress harvesting the root directory as an element. See the full doc for heat here: http://wixtoolset.org/documentation/manual/v3/overview/heat.html - Nir Bar Freelance Developer Mail: nir@panel-sw.com Web: www.panel-sw.com - C+

[WiX-users] heat fragments go one directory too low

Hi, I'm harvesting (WiX3.8) a whole lot of dynamically generated documentation files, which are in a subdirectory NEWDOCS. I'm using the following command-line: heat dir "./newdoCs" -gg -template fragment -out ./docs.wxs -sfrag -suid -cg HelpFiles -var wix.MySource -dr DOCFOLDER -directoryid

Re: [WiX-users] Heat over 64 bit dll

Well, the latter approach will run the internal custom actions on the assemblies. -- John Merryweather Cooper Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |jocoo...@jackhenry.com From: samp

Re: [WiX-users] Heat over 64 bit dll

0 |jocoo...@jackhenry.com -Original Message- From: Phil Wilson [mailto:phildgwil...@gmail.com] Sent: Thursday, December 18, 2014 10:58 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Heat over 64 bit dll The COM data (classids etc) is typically the same

Re: [WiX-users] Heat over 64 bit dll

The COM data (classids etc) is typically the same for both architectures, so massaging the 32-bit output a little should be all that's required. --- Phil Wilson On Thu, Dec 18, 2014 at 8:21 AM, John Cooper wrote: > Well, the general problem is that COM registry entries are going to b

Re: [WiX-users] Heat over 64 bit dll

Well, the general problem is that COM registry entries are going to be in the 32-bit hive (traditionally, COM has been 32-bit). A heat running as a 64-bit process should be able to see these entries (the converse would not be true). However, heat hasn't changed much since Wix 3.5, and I suspec

[WiX-users] Heat harvest a directory generating PayloadGroup

I have an exe (or msi) package that need to have some folders in the same root to works. I need to add it to the Burn bootstrapper.As I take this msi from an automatic build the content of the folders that are deployed with the msi could change so I need to use Heat to harvest the main folder wh

[WiX-users] Heat and ".vb" code

I've haven't been able to find any cases online where heat was used with a "project.vbprog" file rather than a "project.csprog" file but neither have I found any explicit statement that heat only works with C# project files. Can anyone clear this up for me? Thanks, Jonathan Anderson Software De

Re: [WiX-users] heat throws error on Windows 7

Just happy to be of assistance :) From: eric [eric.bu...@lmco.com] Sent: June 30, 2014 10:07 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] heat throws error on Windows 7 Thanks for the help, scubasteve! In my hunt, I realized that it

Re: [WiX-users] heat throws error on Windows 7

Thanks for the help, scubasteve! In my hunt, I realized that it was choking on some ruby files that I hadn't intended to include anyway. Once I removed them, the harvesting process went fine. I didn't investigate further to see if it was indeed permissions issues, but one way or the other, you l

Re: [WiX-users] heat throws error on Windows 7

@lists.sourceforge.net Subject: Re: [WiX-users] heat throws error on Windows 7 It does, indeed. I realized that it runs fine in Cygwin, but not from the Windows commandline. Any idea why that might be? I would prefer not to have to set up Cygwin on our build server. scubasteve2 wrote > Does "./

Re: [WiX-users] heat throws error on Windows 7

It does, indeed. I realized that it runs fine in Cygwin, but not from the Windows commandline. Any idea why that might be? I would prefer not to have to set up Cygwin on our build server. scubasteve2 wrote > Does "./MyFolder" exist? -- View this message in context: http://windows-install

Re: [WiX-users] heat throws error on Windows 7

Does "./MyFolder" exist? From: eric [eric.bu...@lmco.com] Sent: June 21, 2014 11:14 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] heat throws error on Windows 7 I ran heat from the commandline with a command in the following form:

[WiX-users] heat throws error on Windows 7

I ran heat from the commandline with a command in the following form: heat dir ".\MyFolder" -gg -template product -out out.wsx But when I did, I got the following error: Windows Installer XML Toolset Toolset Harvester version 3.8.1128.0 Copyright (c) Outercurve Foundation. All rights

[WiX-users] Heat command line vs HarvestDirectory task

I have been experimenting with and creating a project which uses heat to harvest files. Initially I did the development by creating a batch (cmd) file which calls heat. Now I am in the process of modifying my project file to use the HeatDirectory task, and implement the equivalent of my batch fil

Re: [WiX-users] Heat error

Added -scom and got around the issue. :) J On Fri, Aug 9, 2013 at 11:21 AM, Jeremiahf wrote: > The Class element's ForeignServer or Server attribute was not found; one > of these is required. > > > Hello all, > > I have looked around online and found some developers have run into this. > I hav

[WiX-users] Heat error

The Class element's ForeignServer or Server attribute was not found; one of these is required. Hello all, I have looked around online and found some developers have run into this. I have not been able to find a solution to get around this error. I am harvesting a directory using the Pre-build E

Re: [WiX-users] Heat and harvesting

Found the answer, I was doing it all wrong. The code that got it working: Keep in mind that I'm still working on my heat commands, but it this is the way that heat is called on wix. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-and-harves

[WiX-users] Heat and harvesting

Hello everyone, In my current project, I am dueling with harvesting VisualStudio Outputs with heat. The theme is somewhat controversial, as I've seen people saying the process is not deterministic and that it would be better to do it by hand, but I have far to many projects and files to deal with.

Re: [WiX-users] Heat DiskId

gestions: > 1. Use xsl transform > 2. Use the MediaTemplate element as that automatically splits files across > cabs. > > Neil > > -Original Message- > From: Veli-Matti Visuri [mailto:veli-matti.vis...@futuremark.com] > Sent: 18 July 2013 09:51 > To: wix-users@

Re: [WiX-users] Heat DiskId

Subject: [WiX-users] Heat DiskId Hi, I couldn't find anywhere is there going to be in the future a parameter for the heat tool or HeatDirectory task to define the DiskId attribute? I am asking this because my installer is over 2 gigabytes and the data needs to be separated into two ca

[WiX-users] Heat DiskId

Hi, I couldn't find anywhere is there going to be in the future a parameter for the heat tool or HeatDirectory task to define the DiskId attribute? I am asking this because my installer is over 2 gigabytes and the data needs to be separated into two cabinet files and it seems that there is no way

Re: [WiX-users] Heat + Harvesting a 64bit COM component

to get the toolset to do this natively. -Original Message- From: Jason Stephenson [mailto:jason.stephen...@it2tms.com] Sent: Monday, July 01, 2013 7:18 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Heat + Harvesting a 64bit COM component Hi All, Hopefully this is the

[WiX-users] Heat + Harvesting a 64bit COM component

Hi All, Hopefully this is the correct place to post this.. I've currently got a 64bit win32 com component that requires registering via regsvr32.exe I've been reading that the correct way to use this in WIX is using heat.exe to extract what will end up in the registry and including that in my

Re: [WiX-users] Heat - Include question

> forcing write access to non-admins in places it doesn't belong. > > Please don't make your customer's systems insecure. It makes a worse world > for all of us. > > Blair Murri > >> From: pally.sand...@iesve.com >> To: wix-users@lists.sourceforge.net

Re: [WiX-users] Heat - Include question

tal Solutions Limited. Registered in Scotland No. > SC151456 > Registered Office - Helix Building, West Of Scotland Science Park, Glasgow > G20 0SP > Email Disclaimer > > -Original Message- > From: BGINFO4X [mailto:bginf...@kztsoftware.com] > Sent: 01 June 2013

Re: [WiX-users] Heat - Include question

Original Message- From: BGINFO4X [mailto:bginf...@kztsoftware.com] Sent: 01 June 2013 10:05 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Heat - Include question >Re: [WiX-users] Heat - Include question >From: Mike Carlson - 2013-05-28 20:01 >It's not a

Re: [WiX-users] Heat -ke error (empty directories)

Sorry, I didn't see your emails. I respond: > 1 - use the -suid flag with heat.exe to make your id's more readable. I tried it and don't help. Even, I don't see the benefits of NO generating UIDs in a .msi. > 2 - what's the Component throwing that error actually contain? The opening > tag doesn

Re: [WiX-users] Heat - Include question

>Re: [WiX-users] Heat - Include question >From: Mike Carlson - 2013-05-28 20:01 >It's not a good idea for your application to write to allow non-elevated >users to write to its installed application folder under program files >folder. Allowing users to overwrite the appli

Re: [WiX-users] Heat - Include question

It's not a good idea for your application to write to allow non-elevated users to write to its installed application folder under program files folder. Allowing users to overwrite the application binaries is a security hole for any customers who might have untrusted users on the machine. Did you i

Re: [WiX-users] Heat -ke error (empty directories)

r XML toolset. Subject: Re: [WiX-users] Heat -ke error (empty directories) Hello again, I need your help. The problem with "heat -ke" + light seems to be related to the fact that the guid of empty directories can't be an "*". It must be a normal GUID, so light doesn't cra

Re: [WiX-users] Heat -ke error (empty directories)

Hello again, I need your help. The problem with "heat -ke" + light seems to be related to the fact that the guid of empty directories can't be an "*". It must be a normal GUID, so light doesn't crash with the error LGHT0230. Do you know how to create a GUID (not *) for empty directories with heat

Re: [WiX-users] Heat -ke error (empty directories)

ns Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: BGINFO4X [mailto:bginf...@kztsoftware.com] Sent: 27 May 2013 17:29 To: General discussion for Windows Installer XML too

Re: [WiX-users] Heat - Include question

n Data folders are for. Phil -Original Message- From: BGINFO4X [mailto:bginf...@kztsoftware.com] Sent: Monday, May 27, 2013 6:52 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Heat - Include question Hello everyone, I'm already finish, , but

[WiX-users] Heat -ke error (empty directories)

Hello, I'm using HEAT with the option -ke (keep empty directories) with the following commands: @echo off echo "##" echo "HEAT!" "C:\Program Files\WiX Toolset v3.7\bin\heat" dir "BGINFO4XW" -cg SampleGroup -out SampleGroup

Re: [WiX-users] Heat - Include question

Hello everyone, I'm already finish, , but I have a little problem related to the NTFS Permissions: The normal permissions inside %program files% are: Administrators -> FULL CONTROL ; Users -> Read But when the application is executed as a normal user, it doesn't work: Normal users NE

Re: [WiX-users] Heat - Include question

Ok, thanks a lot. Regards. 2013/5/21 Mike Carlson : > Ah, then you do want to support upgrades. Get your upgrade scenario right, > and you won't have to worry about having a consistent shortcut name. > > Read up on "Major Upgrades" here: > http://msdn.microsoft.com/en-us/library/windows/desktop/a

Re: [WiX-users] Heat - Include question

Ah, then you do want to support upgrades. Get your upgrade scenario right, and you won't have to worry about having a consistent shortcut name. Read up on "Major Upgrades" here: http://msdn.microsoft.com/en-us/library/windows/desktop/aa369786(v=vs.85).aspx. This will cause the old version to be un

Re: [WiX-users] Heat - Include question

2013/5/21 Mike Carlson : > You should be able to. Create the shortcut in your own authoring file. To > point to the file in the generated authoring, see the "Target" attribute of > the shortcut element in wix.chm. > Thanks a lot , I will try it. I have a conceptual question regarding shortcuts:

Re: [WiX-users] Heat - Include question

You should be able to. Create the shortcut in your own authoring file. To point to the file in the generated authoring, see the "Target" attribute of the shortcut element in wix.chm. On Tue, May 21, 2013 at 4:37 AM, BGINFO4X wrote: > > You should change it to this: > > > > > >

Re: [WiX-users] Heat - Include question

> You should change it to this: > > > > > Thanks, it works! > Also, you should pass in "-srd" on the heat commandline (suggestion #3 > above), or else you're going to get a "BGINFO4XW" directory inside the > directory you intend to install to. Done. > > Fina

Re: [WiX-users] Heat - Include question

Your problem is that "basedir" isn't a child of "INSTALLDIR", it's a child of "ProgramFilesFolder". Here is your current code: You should change it to this: Also, you should pass in "-srd" on the heat commandline (suggestion #3 above), or e

Re: [WiX-users] Heat - Include question

> 1) Add (for example) "-dr foo" to your heat commandline to generate them > under a directory of ID "foo" Done: "C:\Program Files\WiX Toolset v3.7\bin\heat" dir "BGINFO4XW" -cg SampleGroup -out SampleGroup.wxs -gg -dr basedir > 2) In your main authoring file, you then need to define a director

Re: [WiX-users] Heat - Include question

2013/5/17 Jeremiahf : > Ah, so your building your MSI via command line. Good to hear you figured it > out. Yes, I'm doing only a .msi package, not a visual project with c# or similar ... Thanks. -- AlienVault Unified Sec

Re: [WiX-users] Heat - Include question

Ah, so your building your MSI via command line. Good to hear you figured it out. J On Fri, May 17, 2013 at 12:48 PM, BGINFO4X wrote: > Hello, > > I see the problems: > > The First one was that light needs all the *.wixobj > The Second one was that light needs the -b parameter. > > Now, I do th

Re: [WiX-users] Heat - Include question

The problem you're running into is that the generated components are by default generated under a directory under "TARGETDIR", not "INSTALLDIR". To override this: 1) Add (for example) "-dr foo" to your heat commandline to generate them under a directory of ID "foo" 2) In your main authoring file,

Re: [WiX-users] Heat - Include question

Hello, I see the problems: The First one was that light needs all the *.wixobj The Second one was that light needs the -b parameter. Now, I do the following: "C:\Program Files\WiX Toolset v3.7\bin\heat" dir "BGINFO4XW" -cg SampleGroup -out SampleGroup.wxs -gg "C:\Program Files\W

Re: [WiX-users] Heat - Include question

Are you not referencing SampleGroup.wxs? J On Fri, May 17, 2013 at 8:55 AM, BGINFO4X wrote: > Hello everyone, > > I'm a new to WIX and I'm a little lost. > > I want to create a .msi file from my project (with lots of files and > folders), so I use HEAT. > Heat works as exepcted an

Re: [WiX-users] Heat - Include question

...@kztsoftware.com] Sent: 17 May 2013 14:56 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Heat - Include question Hello everyone, I'm a new to WIX and I'm a little lost. I want to create a .msi file from my project (with lots of files and folders), so I use HEAT. Hea

[WiX-users] Heat - Include question

Hello everyone, I'm a new to WIX and I'm a little lost. I want to create a .msi file from my project (with lots of files and folders), so I use HEAT. Heat works as exepcted and a new file is created (SampleGroup.wxs). Then I try to "compile all" : "C:\Program Files\WiX Toolset v3.7\bin\candle" S

Re: [WiX-users] Heat creates duplicate IDs

Message- > From: Nick Miller [mailto:nmil...@livetechnology.com] > Sent: Monday, May 13, 2013 8:39 AM > To: General discussion for Windows Installer XML toolset. > (wix-users@lists.sourceforge.net) > Subject: [WiX-users] Heat creates duplicate IDs > > Hi All, > > D

Re: [WiX-users] Heat creates duplicate IDs

ay, May 13, 2013 8:39 AM To: General discussion for Windows Installer XML toolset. (wix-users@lists.sourceforge.net) Subject: [WiX-users] Heat creates duplicate IDs Hi All, Does anyone know how Heat generates the component and file ID's? Here is the situation: I have two folders, and those

[WiX-users] Heat creates duplicate IDs

Hi All, Does anyone know how Heat generates the component and file ID's? Here is the situation: I have two folders, and those folders contain some of the same files (dll's and such). If I run Heat on both of those directories it creates the same component and file IDs for those like files. Is

Re: [WiX-users] Heat with file path longer than 260 chars report an error

7:20 AM, Marco Tognacci wrote: > > > > > So isn't there any way to make Heat working with long paths? Any plan > for > > > next release? > > > > > > > From: r...@robmensching.com > > > > Date: Fri, 3 May 2013 11:12:13 -0700

Re: [WiX-users] Heat with file path longer than 260 chars report an error

Thanks, do you know when NETFX 5.0 and MSI 6.0 are planned to public realese? > From: r...@robmensching.com > Date: Sun, 5 May 2013 07:33:42 -0700 > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Heat with file path longer than 260 chars report an > error > &

Re: [WiX-users] Heat with file path longer than 260 chars report an error

om: r...@robmensching.com > > Date: Fri, 3 May 2013 11:12:13 -0700 > > To: wix-users@lists.sourceforge.net > > Subject: Re: [WiX-users] Heat with file path longer than 260 chars > report an error > > > > Unfortunately, the .NET Framework doesn't handle that. >

Re: [WiX-users] Heat with file path longer than 260 chars report an error

So isn't there any way to make Heat working with long paths? Any plan for next release? > From: r...@robmensching.com > Date: Fri, 3 May 2013 11:12:13 -0700 > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Heat with file path longer than 260 chars re

Re: [WiX-users] Heat with file path longer than 260 chars report an error

mple, "\\?\D:\very long path". > > -Original Message- > From: Edwin Castro [mailto:egca...@gmail.com] > Sent: Friday, May 03, 2013 1:10 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Heat with file path longer t

Re: [WiX-users] Heat with file path longer than 260 chars report an error

On 2013-05-03 20:10, Edwin Castro wrote: > That character limit on paths is imposed by .NET. :-( I use https://alphafs.codeplex.com/ to work with pathes up to 32000 characters. I hope they will fix it in .NET sometime. Marc

Re: [WiX-users] Heat with file path longer than 260 chars report an error

n for Windows Installer XML toolset. Subject: Re: [WiX-users] Heat with file path longer than 260 chars report an error That character limit on paths is imposed by .NET. :-( On Fri, May 3, 2013 at 10:56 AM, Marco Tognacci wrote: > I have used HeatDirectory to harvest a folder with many subdir

Re: [WiX-users] Heat with file path longer than 260 chars report an error

t. Subject: Re: [WiX-users] Heat with file path longer than 260 chars report an error That character limit on paths is imposed by .NET. :-( On Fri, May 3, 2013 at 10:56 AM, Marco Tognacci wrote: > I have used HeatDirectory to harvest a folder with many subdirectories > and files, bu

Re: [WiX-users] Heat with file path longer than 260 chars report an error

Unfortunately, the .NET Framework doesn't handle that. On Fri, May 3, 2013 at 10:56 AM, Marco Tognacci wrote: > I have used HeatDirectory to harvest a folder with many subdirectories and > files, but Heat.exe report an error because the filepath of an item is > larger than 260 chars (with the n

Re: [WiX-users] Heat with file path longer than 260 chars report an error

That character limit on paths is imposed by .NET. :-( On Fri, May 3, 2013 at 10:56 AM, Marco Tognacci wrote: > I have used HeatDirectory to harvest a folder with many subdirectories and > files, but Heat.exe report an error because the filepath of an item is > larger than 260 chars (with the na

[WiX-users] Heat with file path longer than 260 chars report an error

I have used HeatDirectory to harvest a folder with many subdirectories and files, but Heat.exe report an error because the filepath of an item is larger than 260 chars (with the name and the full subdirectories path)Is there any way to harvest a folder with may subdirectories as the single filep

Re: [WiX-users] heat reg output includes deprecated Action attribute

Done.. https://sourceforge.net/p/wix/bugs/3289/ -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-reg-output-includes-deprecated-Action-attribute-tp7585545p7585551.html Sent from the wix-users mailing list archive at Nabble.com. -

Re: [WiX-users] heat reg output includes deprecated Action attribute

Can you raise a bug - I think I added this code to WiX3 so will take a look. -Original Message- From: rowbot [mailto:james.row...@microfocus.com] Sent: 02 May 2013 11:30 To: wix-users@lists.sourceforge.net Subject: [WiX-users] heat reg output includes deprecated Action attribute Using

Re: [WiX-users] heat reg output includes deprecated Action attribute

SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: rowbot [mailto:james.row...@microfocus.com] Sent: 02 May 2013 11:34 To: wix-users@lists.sourceforge.net Subject: [WiX-users] heat reg output includes d

[WiX-users] heat reg output includes deprecated Action attribute

Using 3.7 to 'heat reg' and candle throws CNDL1138 warnings because RegistryKey/@Action attribute has been deprecated.. File a bug? Thanks, -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-reg-output-includes-deprecated-Action-attribute-tp75

Re: [WiX-users] Heat, XSLT, and Difxapp

I change my mind. Hardcored oemsetup.inf in global wxs with difxapp:driver. Then, heat harvest driver's file and exclude oemsetup.inf. Obvious. Le %:Date:, Gabriel Ivanes <[1]g...@fastmail.net> a écrit: Hi there, I want to automat heat with difxapp. I use heat this way : heat d

[WiX-users] Heat, XSLT, and Difxapp

Hi there, I want to automat heat with difxapp. I use heat this way : heat dir .\Sources -cg cmp_files_driver_x86 -dr TARGETDIR -gg -ke -out Projet\Files_driver.wxs -var var.Sources = ".\Sources" -t Build\Set_difxapp_to_inf.xsl. But XSLT failed because i don't know it well. First, i want

[WiX-users] Heat on network drive?

Can we heat.exe for one on network path like \\c2tfsci\c$\Builds\16\\Binaries\ContinuousIntegration\_PublishedWebsites\Web. if so how would be the source path to above location look like in fragments.wxs? Thanks in advance.. Chatra -- View this message in context: http://windows-installer-xm

[WiX-users] Heat WXS listing does not match Orca MSI File content

I'm new to WiX. Using WiX Toolset 3.6 on Luntbuild Build Server, Tortoise SVN, Nant build script calling WiX Heat, Candle, Light. The source is a ASP.NET website but I have chosen to use the Heat -dir option because it is being built on a Build Server and not the multiple target Web Server(s). Wh

Re: [WiX-users] Heat Website Harvester Status?

Hi Aaron, Did you find the solution ... I was looking for solution for website Harvesting. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-Website-Harvester-Status-tp3177602p7583566.html Sent from the wix-users mailing list archive at Nabble.

Re: [WiX-users] Heat-harvesting with subfolder in the -Source atribute

There are number of ways of achieving results results. 1) As told by Gabriel 2) Don't include -srd switch to harvest root directory as element. 3) use -var in Heat and -d in candle. e.g for 3 heat.exe dir "$(SolutionDir)MyProject\MyDirectory" -ag -sfrag -srd -var "var.MyProjectDir" -out $(ProjectD

Re: [WiX-users] Heat-harvesting with subfolder in the -Source atribute

Hi, And with this : *heat.exe dir "$(SolutionDir)MyProject" -ag -sfrag -srd -var "var.MyProject.ProjectDir" -out $(ProjectDir)HarvestedFiles.wxs"* Or you could add a subdir "Sources" in your SolutionDir : C:\\SolutionDir\MyProject\Sources\MyDirectory *heat.exe dir "$(SolutionDir)MyProject

[WiX-users] Heat-harvesting with subfolder in the -Source atribute

Hi, I have a project structure which is like this: *C:\\SolutionDir\MyProject\MyDirectory* In a pre-build event I use this: *heat.exe dir "$(SolutionDir)MyProject\MyDirectory" -ag -sfrag -srd -var "var.MyProject.ProjectDir" -out $(ProjectDir)HarvestedFiles.wxs"* The output in HarvestedFiles

Re: [WiX-users] heat extension - COM exe servers and 64-bit COM support

Hi Rob -- I sent an email from my work address a while back, but I guess it didn't get through. Anyhow, yes I am interested. Probably better to use this address: wix at rhysw dot com. Thanks ! -Rob Y. Rob Mensching-7 wrote > If you can wait a few more weeks, this might be an interesting thing t

Re: [WiX-users] heat extension - COM exe servers and 64-bit COM support

If you can wait a few more weeks, this might be an interesting thing to incorporate into WiX v4. If interested, ping me and I can connect you with the correct people at Outercurve (who maintain the WiX assignment process now) to get the process rolling. On Mon, Nov 12, 2012 at 9:05 AM, wrote: >

Re: [WiX-users] heat extension - COM exe servers and 64-bit COM support

I maintain copyright to ISWIX but license it to all to use. Chris From: robert_y...@agilent.com Sent: Monday, November 12, 2012 11:43 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] heat extension - COM exe servers and 64-bit COM support Hi al

[WiX-users] heat extension - COM exe servers and 64-bit COM support

Hi all - about a year ago I wrote a heat extension (based on various code I found on the web) for our internal use which harvests 32-bit COM EXE servers and pre-initializes the registry with the ATL Registrar before harvesting. Lately I updated it with support for 64-bit COM servers (DLL and EX

Re: [WiX-users] heat failing over a network

On 08-Nov-12 13:38, Matthew Clark wrote: > I have an issue with a .net dll failing to be harvested over the network. > Harvesting works fine if the file is local, but when it is at a network > location it fails with the error: .NET doesn't let you load assemblies from remote sources by default

[WiX-users] heat failing over a network

Hello all: I have an issue with a .net dll failing to be harvested over the network. Harvesting works fine if the file is local, but when it is at a network location it fails with the error: Warning HEAT5151: Could not harvest data from a file that was expected to be an assembly: \\blah\foo.dl

[WiX-users] Heat and Recursion

Is there a way to tell heat not to recurse through a directory tree but to only harvest the top-level files? Sent from my iPhone On 6 Sep 2012, at 09:13, "wix-users-requ...@lists.sourceforge.net" wrote: > Send WiX-users mailing list submissions to >wix-users@lists.sourceforge.net > > To

Re: [WiX-users] heat and xslt transform to keep only pdb files

2012 12:15 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] heat and xslt transform to keep only pdb files Have you tried: -Original Message- From: Naim Kingston [mailto:naim.kings...@ancamotion.com] Sent: 03 August 2012 01:55 T

Re: [WiX-users] heat and xslt transform to keep only pdb files

Have you tried: -Original Message- From: Naim Kingston [mailto:naim.kings...@ancamotion.com] Sent: 03 August 2012 01:55 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] heat and xslt transform to keep only pdb files I'm using heat to tr

[WiX-users] heat and xslt transform to keep only pdb files

I'm using heat to try and harvest a directory of all the pdb files. I know that there is an option for heat to look into the vcproj files to get them, but I may need to expand this in the future to deal with other file types as well, such as linker map files, and the like. What I've got so far

[WiX-users] heat parameters for harvesting a reg file

I want to harvest a reg file using heat. The wxs file is generated using: heat reg data.reg" -ag -sfrag -cg Registry -o Registry.wxs The call to heat succeeds but when I build the installer the following error message occurs: Registry.wxs (4): The Directory element requires the Name attribute b

[WiX-users] Heat in WiX v3.6 RC0 generates and extra TypeLib entry

All, I just installed WiX v3.6 RC0 and tried using Heat on some of my old COM dll's I noticed that it generates an extra TypeLib entry compared to what WiX v3.6 beta was generating. Specifically I get this extra entry: And it's inserted outside the section, so it also generate

Re: [WiX-users] heat question

itself to author it's > various merge modules and product installer. > > > > From: "Joel Budreau" > > Sent: Wednesday, February 15, 2012 1:47 PM > > To: "WiX Users" > > Subject: [WiX-users] heat questi

Re: [WiX-users] heat question

product installers come together as ISWIX uses ISWIX and WIX itself to author it's various merge modules and product installer. From: "Joel Budreau" Sent: Wednesday, February 15, 2012 1:47 PM To: "WiX Users" Subject: [WiX-

[WiX-users] heat question

Hi, I'm using WiX 3.0 and utilizing heat.exe to harvest a directory in my build tree. My goal is to generate a MSM using the resulting .wxs file. I have a couple of MSIs that will use this MSM, and each MSI will want to install the MSM files into a separate directory. Here's my problem: - B

Re: [WiX-users] Heat -generate

On 03-Nov-11 10:35, David L. Beckwith wrote: > "error LGHT0103: The system cannot find the file ..." > > I suspect this file name is too long (72 characters). However, when this That's not a problem as long as the full path fits in MAXPATH characters. -- sig://boB http://joyofsetup.com/ --

  1   2   3   4   5   >