Re: [WiX-users] heat.exe: How to generate unique but human readable IDs for directories, components and files
Thanks for your confirmation. Kind Regards, Sampat -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-exe-How-to-generate-unique-but-human-readable-IDs-for-directories-components-and-files-tp7600068p7600104.html Sent from the wix-users mailing list archive at Nabble.com. -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe: How to generate unique but human readable IDs for directories, components and files
I just realized that WiX appends a merge module GUID to all IDs during wxs compilation. So it's not the problem that heat.exe generates non unique IDs with -suid option, the IDs will become unique when wxs will be compiled to merge module. So, yes -suid option fully meets my requirements. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-exe-How-to-generate-unique-but-human-readable-IDs-for-directories-components-and-files-tp7600068p7600098.html Sent from the wix-users mailing list archive at Nabble.com. -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe: How to generate unique but human readable IDs for directories, components and files
I think you can use -SUID parameter to heat. sampat -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-exe-How-to-generate-unique-but-human-readable-IDs-for-directories-components-and-files-tp7600068p7600071.html Sent from the wix-users mailing list archive at Nabble.com. -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] heat.exe: How to generate unique but human readable IDs for directories, components and files
When heat.exe harvests directory it generates unique but human unreadable
directories, components and files IDs:
Directory Id=dir44C327128861C709AEDB0EA3555D0587 Name=MyDirectory
Component Id=cmp04CA6ED916B15D4A669AAC63FB00ECD3
Guid={8EE35AF9-6CEF-43E7-91FA-C341B8D764FF}
File Id=fil740188E003510CC996EF84EFEA43F833 KeyPath=yes
Source=SourceDir\File.txt /
/Component
/Directory
There is option -suid, that forces heat.exe to generate human readable but
non unique IDs like *File.txt_2*.
Does heat.exe have an option to generate human readable and unique IDs like
*File.txt_04CA6ED916B15D4A669AAC63FB00ECD3*? I generate wxs file for my
merge module through heat.exe and IDs like
*fil740188E003510CC996EF84EFEA43F833* looks ugly when my merge module is
opened in Orca or when I look over an installation log. IDs like
*File.txt_04CA6ED916B15D4A669AAC63FB00ECD3* would improve visibility and
convenience significantly.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-exe-How-to-generate-unique-but-human-readable-IDs-for-directories-components-and-files-tp7600068.html
Sent from the wix-users mailing list archive at Nabble.com.
--
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe: How to generate unique but human readable IDs for directories, components and files
You can run heat with unique IDs and then apply a XSLT transform to prefix each ID with the file name. - 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.n2.nabble.com/heat-exe-How-to-generate-unique-but-human-readable-IDs-for-directories-components-and-files-tp7600068p7600069.html Sent from the wix-users mailing list archive at Nabble.com. -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe: How to generate unique but human readable IDs for directories, components and files
Yeah, I know. For now there is some post-build script that corrects all IDs every time my merge module built. But this is workaround. The most proper way is native support of unique human-readable names in heat.exe I think. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-exe-How-to-generate-unique-but-human-readable-IDs-for-directories-components-and-files-tp7600068p7600070.html Sent from the wix-users mailing list archive at Nabble.com. -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Heat.exe harvesting question
Hi, I have the following pre-build event for wix. $(WIX)bin\heat.exe dir $(ProjectDir)/../src/bin/$(ConfigurationName)/MyAppInt -cg MyAppFiles -gg -scom -sreg -sfrag -srd -dr AV -var var.MyAppFilesDir -out $(ProjectDir)Fragments/MyAppFiles.wxs I have my MyApp.exe and MyApp.exe.config files in the /src/bin/Debug/MyAppInt. However, when the prebuild step is carried out, for some reason, wix/heat.exe thought that my executable and config should be MyAppInt.exe and MyAppInt.exe.config. Is there any way to fix this? Thank you very much for your help in advance. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-exe-harvesting-question-tp7596962.html Sent from the wix-users mailing list archive at Nabble.com. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe harvesting question
Any reason you aren't using the HeatDriectory task? HeatDirectory NoLogo=true ToolPath=$(WixToolPath) VerboseOutput=true AutogenerateGuids=true GenerateGuidsNow=false OutputFile=$(IntermediateOutputPath)All.wxs SuppressFragments=true Directory=Z:\$(Version)\Data\ ComponentGroupName=ProductComponents DirectoryRefId=CommonData PreprocessorVariable=var.SourceDataFolder SuppressCom=true SuppressRootDirectory=true SuppressRegistry=true / -Original Message- From: newuser2014 [mailto:wamplersovere...@gmail.com] Sent: Wednesday, September 24, 2014 10:24 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Heat.exe harvesting question Hi, I have the following pre-build event for wix. $(WIX)bin\heat.exe dir $(ProjectDir)/../src/bin/$(ConfigurationName)/MyAppInt -cg MyAppFiles -gg -scom -sreg -sfrag -srd -dr AV -var var.MyAppFilesDir -out $(ProjectDir)Fragments/MyAppFiles.wxs I have my MyApp.exe and MyApp.exe.config files in the /src/bin/Debug/MyAppInt. However, when the prebuild step is carried out, for some reason, wix/heat.exe thought that my executable and config should be MyAppInt.exe and MyAppInt.exe.config. Is there any way to fix this? Thank you very much for your help in advance. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-exe-harvesting-question-tp7596962.html Sent from the wix-users mailing list archive at Nabble.com. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe harvesting case sensitive vb6 dll's
Hi Ravi, Heat creates its unique file/component references based on the source name of the file. So if you change the name, or the relative location of the source file, then the file reference may well change. I believe there is a way to force it to not generate new references, however I've found that generally it's not a problem since it's really not so common to be modifying the filename anyway. It's probably very important to note however that if you allow WiX to dynamically create your component IDs that you shouldn't be renaming / moving the source files for these components unless you will be forcing a major upgrade. Since changing component IDs on a minor upgrade is getting into dangerous territory. Regards, Bevan Weiss SAGE Automation Date: Wed, 19 Mar 2014 10:11:38 +0530 From: Ravishankar ravishankar.krishnasw...@idsfortune.com Subject: [WiX-users] Heat.exe harvesting case sensitive vb6 dll's Hi, Am facing a strange issue, i have a dll(VB6 created) with name = LITA300.dll and when i extract using Heat.exe it generates a set of Component ID and FileID Now if i change my dll name = lita300.dll , the heat.exe is generating a different set of Component ID and FileID C:\Program Files (x86)\WiX Toolset v3.6\bin\heat.exe dir C:\Temp -dr INSTALLLOCATION -cg FORTUNEFilesGroup -gg -g1 -sfrag -scom -srd -svb6 -var var.SourceItemsDir -out C:\Temp\Components.wxs i have placed my dll under C:\Temp folder Can anyone please help me, is extracting dll files using Heat.exe is case sensitive?, i mean should the filenames be case-sensitive? Thanks and Regards Ravi Shankar -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Heat.exe harvesting case sensitive vb6 dll's
Hi, Am facing a strange issue, i have a dll(VB6 created) with name = LITA300.dll and when i extract using Heat.exe it generates a set of Component ID and FileID Now if i change my dll name = lita300.dll , the heat.exe is generating a different set of Component ID and FileID C:\Program Files (x86)\WiX Toolset v3.6\bin\heat.exe dir C:\Temp -dr INSTALLLOCATION -cg FORTUNEFilesGroup -gg -g1 -sfrag -scom -srd -svb6 -var var.SourceItemsDir -out C:\Temp\Components.wxs i have placed my dll under C:\Temp folder Can anyone please help me, is extracting dll files using Heat.exe is case sensitive?, i mean should the filenames be case-sensitive? Thanks and Regards Ravi Shankar -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe Exception with MSBuild and HeatDirectory
Yes E: drive is local not a network share. The location of the heat.exe is correct, when i copy the full path i get from the error and run heat.exe from there it works i.e. the path is correct. I have built the project with MSBuild without any problems the issue came when introducing HeatDirectory i.e. putting heat.exe to use. On Tue, Feb 18, 2014 at 7:57 PM, Bevan Weiss kaize...@hotmail.com wrote: Is E:\ local? I suspect it might be a network share. If the MSBuild process is using elevated privileges then all network shares (created when non-elevated) disappear. This only occurs with WindowsServer 2008R2 and above I believe (and I'm not sure if it's in Windows 7, but it's definitely in Windows 8 and above) Is v3.7.1224.0 the version that you are expecting? Bevan -Original Message- Date: Tue, 18 Feb 2014 16:43:27 +0100 From: Ilir Bekteshi ilir...@gmail.com Subject: [WiX-users] Heat.exe Exception with MSBuild and HeatDirectory I have a HeatDirectory in wixproj and it works fine when i build from VS but when i try to build with MSbuild it crashes with the error below. Does any one have any idea why is this happening? Unhandled Exception: System.BadImageFormatException: Could not load file or assembly 'file:///E:\TFS\\tools\wix\3.7.1224.0\bin\Heat.exe' or one of its dependencies. An attempt was made to load a program with an incorrect format. at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark stackMark) at System.Reflection.Assembly.LoadFrom(String assemblyFile) at Microsoft.Tools.WindowsInstallerXml.Build.Tasks.WixToolTask.ExecuteToolThre ad(Object parameters) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart(Object obj) -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Heat.exe Exception with MSBuild and HeatDirectory
I have a HeatDirectory in wixproj and it works fine when i build from VS but when i try to build with MSbuild it crashes with the error below. Does any one have any idea why is this happening? Unhandled Exception: System.BadImageFormatException: Could not load file or assembly 'file:///E:\TFS\\tools\wix\3.7.1224.0\bin\Heat.exe' or one of its dependencies. An attempt was made to load a program with an incorrect format. at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark stackMark) at System.Reflection.Assembly.LoadFrom(String assemblyFile) at Microsoft.Tools.WindowsInstallerXml.Build.Tasks.WixToolTask.ExecuteToolThread(Object parameters) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart(Object obj) -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe Exception with MSBuild and HeatDirectory
Is E:\ local? I suspect it might be a network share. If the MSBuild process is using elevated privileges then all network shares (created when non-elevated) disappear. This only occurs with WindowsServer 2008R2 and above I believe (and I'm not sure if it's in Windows 7, but it's definitely in Windows 8 and above) Is v3.7.1224.0 the version that you are expecting? Bevan -Original Message- Date: Tue, 18 Feb 2014 16:43:27 +0100 From: Ilir Bekteshi ilir...@gmail.com Subject: [WiX-users] Heat.exe Exception with MSBuild and HeatDirectory I have a HeatDirectory in wixproj and it works fine when i build from VS but when i try to build with MSbuild it crashes with the error below. Does any one have any idea why is this happening? Unhandled Exception: System.BadImageFormatException: Could not load file or assembly 'file:///E:\TFS\\tools\wix\3.7.1224.0\bin\Heat.exe' or one of its dependencies. An attempt was made to load a program with an incorrect format. at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark stackMark) at System.Reflection.Assembly.LoadFrom(String assemblyFile) at Microsoft.Tools.WindowsInstallerXml.Build.Tasks.WixToolTask.ExecuteToolThre ad(Object parameters) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart(Object obj) -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] heat.exe : warning HEAT5151
Hi All, I am creating a WIX installer. In the heat part i am getting the below warning: heat.exe : warning HEAT5151 : Could not harvest data from a file that was expected to be an assembly: D:\configRelease\command_processors\bpolympic\OraclePull.dll. If this file is not an assembly you can ignore this warning. Otherwise, this error detail may be helpful to diagnose the failure: Could not load file or assembly 'PFWCommandProcessor, Version=5.3.1.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified. The heat is harvesting D:\configRelease\command_processors\bpolympic\OraclePull.dll . The installer gets created and on running the installer the path created is C:\Energy Solutions International\PFWService\config\command_processors\bpolympic (this is what i have defined) and the file is also there i.e the OraclePull.dll(of the same size as source). The file C:\Energy Solutions International\PFWService\config\command_processors\ExampleCommandProcessor\PFW\PFWCommandProcessor.dll is also there. The version though shown for this file is 1.0.0.0 Do i need to worry about this warning? If so please let me know how i can handle the same. Regards, SuvraJyoti -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe : warning HEAT5151
Not all version numbers are created equal. 5.3.1.0 probably reflects the AssemblyVersion which impacts the strong naming. 1.0.0.0 reflects the AssemblyFileVersion. You should be concerned that your build process is not incrementing the AssemblyFileVersion. This is the version that the installer uses to determine whether to overwrite an existing assembly. There are a number of ways to get the AssemblyFileVersion to increment. But if you don't choose one, your patching and upgrading is going to be unreliable to say the least. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in] Sent: Monday, December 16, 2013 4:48 AM To: General discussion about the WiX toolset. Subject: [WiX-users] heat.exe : warning HEAT5151 Hi All, I am creating a WIX installer. In the heat part i am getting the below warning: heat.exe : warning HEAT5151 : Could not harvest data from a file that was expected to be an assembly: D:\configRelease\command_processors\bpolympic\OraclePull.dll. If this file is not an assembly you can ignore this warning. Otherwise, this error detail may be helpful to diagnose the failure: Could not load file or assembly 'PFWCommandProcessor, Version=5.3.1.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified. The heat is harvesting D:\configRelease\command_processors\bpolympic\OraclePull.dll . The installer gets created and on running the installer the path created is C:\Energy Solutions International\PFWService\config\command_processors\bpolympic (this is what i have defined) and the file is also there i.e the OraclePull.dll(of the same size as source). The file C:\Energy Solutions International\PFWService\config\command_processors\ExampleCommandProcessor\PFW\PFWCommandProcessor.dll is also there. The version though shown for this file is 1.0.0.0 Do i need to worry about this warning? If so please let me know how i can handle the same. Regards, SuvraJyoti -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe : warning HEAT5151
Hi John, Thanks for the reply, could you please let me know what are the different ways to increment the assembly file version? Regards, SuvraJyoti On 16-12-2013 19:47, John Cooper wrote: Not all version numbers are created equal. 5.3.1.0 probably reflects the AssemblyVersion which impacts the strong naming. 1.0.0.0 reflects the AssemblyFileVersion. You should be concerned that your build process is not incrementing the AssemblyFileVersion. This is the version that the installer uses to determine whether to overwrite an existing assembly. There are a number of ways to get the AssemblyFileVersion to increment. But if you don't choose one, your patching and upgrading is going to be unreliable to say the least. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in] Sent: Monday, December 16, 2013 4:48 AM To: General discussion about the WiX toolset. Subject: [WiX-users] heat.exe : warning HEAT5151 Hi All, I am creating a WIX installer. In the heat part i am getting the below warning: heat.exe : warning HEAT5151 : Could not harvest data from a file that was expected to be an assembly: D:\configRelease\command_processors\bpolympic\OraclePull.dll. If this file is not an assembly you can ignore this warning. Otherwise, this error detail may be helpful to diagnose the failure: Could not load file or assembly 'PFWCommandProcessor, Version=5.3.1.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified. The heat is harvesting D:\configRelease\command_processors\bpolympic\OraclePull.dll . The installer gets created and on running the installer the path created is C:\Energy Solutions International\PFWService\config\command_processors\bpolympic (this is what i have defined) and the file is also there i.e the OraclePull.dll(of the same size as source). The file C:\Energy Solutions International\PFWService\config\command_processors\ExampleCommandProcessor\PFW\PFWCommandProcessor.dll is also there. The version though shown for this file is 1.0.0.0 Do i need to worry about this warning? If so please let me know how i can handle the same. Regards, SuvraJyoti -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe XSLT parameters
You can't do it. I use a separate msbuild step to call Saxon to transform my XML. XSLT 2 is much nicer anyway. -Original Message- From: chennam [mailto:chatrapathi.chen...@gmail.com] Sent: 26 February 2013 19:17 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Heat.exe XSLT parameters Hi, I have below command working very well. but not sure can we pass parameters to XSLT Template (FilterFiles.xslt) through command line when we pass xslt template as a parameter to heat command? C:\\heat.exe dir C:\Workspaces\Chatra\Website\SCBUDirect.B2CWeb -cg SCBUDirect -gg -t C:\Workspaces\Chatra\FilterFiles.xslt -out C:\Workspaces\Chatra\WebSiteContent.wxs -directoryid INSTALLLOCATION -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-exe-XSLT-p arameters-tp7583962.html Sent from the wix-users mailing list archive at Nabble.com. - - Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Heat.exe XSLT parameters
Hi, I have below command working very well. but not sure can we pass parameters to XSLT Template (FilterFiles.xslt) through command line when we pass xslt template as a parameter to heat command? C:\\heat.exe dir C:\Workspaces\Chatra\Website\SCBUDirect.B2CWeb -cg SCBUDirect -gg -t C:\Workspaces\Chatra\FilterFiles.xslt -out C:\Workspaces\Chatra\WebSiteContent.wxs -directoryid INSTALLLOCATION -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-exe-XSLT-parameters-tp7583962.html Sent from the wix-users mailing list archive at Nabble.com. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe
Read the heat documentation. Harvest a directory heat dir .\My Files -gg -sfrag -template:fragment -out directory.wxs You don't have to install msi to check the effect of Heat params. See generated SCBUFragment.wxs for details. Anything included in fragment file will be part of your installation. You probably need to avoid suppress params like -scom -sreg -srd -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-exe-tp7583483p7583686.html Sent from the wix-users mailing list archive at Nabble.com. -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe
Hi i am using below statement for harvesting the web application. %WIX%bin\heat.exe dir $(Wixdest) -cg SCBUDirect -gg -scom -sreg -sfrag -srd -dr INSTALLLOCATION -var env.Wixdest -out C:\Workspaces\Chatra\SCBUFragment.wxs And when I install the MSI the resulting folders just contain .dll,.pdb,.xml only .If I require everything from published website folder which is the source then how is the Heat cmd look like. Thanks in Advance Chatra -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-exe-tp7583483p7583583.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe
That, or add the generated wxs file to your project in visual studio. -Original Message- From: Yawar Khan [mailto:yawar.k...@live.com] Sent: 13 February 2013 07:14 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Heat.exe SET WIX=toolset-directory SET WORKING=working-directory *To harvest* %WIX%/bin/heat.exe dir %WORKING%\..\exe\plugin -cg pluginFiles -gg -scom -sreg -sfrag -srd -dr INSTALLLOCATION -var var.PluginProjectDir -out ..\Fragments\pluginFilesFragment.wxs [You may use/skip -sreg, -sfrag, -dr, -var according to your need] *Candle it* %WIX%/bin/candle.exe -dPluginProjectDir=%WORKING%\..\exe\plugin ..\Fragments\pluginFilesFragment.wxs *In setup.wxs add* Feature Id=PluginFeature Title=MySetup Level=1 ComponentGroupRef Id=pluginFiles / /Feature *Light it to build msi* %WIX%/bin/light.exe -o ..\wix-setups\setup setup.wixobj pluginFilesFragment.wixobj -ext WixUtilExtension -ext WixUIExtension -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-exe-tp7583 483p7583536.html Sent from the wix-users mailing list archive at Nabble.com. - - Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe
http://wix.tramontana.co.hu/ Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: chennam [mailto:chatrapathi.chen...@gmail.com] Sent: 11 February 2013 22:19 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Heat.exe Thanks Steve, Intially cmd was notable to recognize Heat.exe as internal or external cmd. Now was able to fingure out heat.exe from Wixtool bin. After harvesting the with Heat.exe a fragment file of .WXS is generated based on the file structure of web application.But I was thinking the MSI file should also be generated when we run heat command as pre build event of Installer setup project. Not sure I am right or wrong ;Can you please say when does the MSI gets created? Thanks in advance. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-exe-tp7583483p7583485.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe
Thanks pal for reference . Now I was able to create the .WXS which is output of Heat.exe and it does contain all the components of the Web directory specified as source directory. But now how could I integrate or refer the generated .WXS ;the out put of Heat.exe in the Installer setup so that when Installer Setup project is compiled the MSI is created which has website directory structure? Thanks in advance. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-exe-tp7583483p7583526.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe
SET WIX=toolset-directory SET WORKING=working-directory *To harvest* %WIX%/bin/heat.exe dir %WORKING%\..\exe\plugin -cg pluginFiles -gg -scom -sreg -sfrag -srd -dr INSTALLLOCATION -var var.PluginProjectDir -out ..\Fragments\pluginFilesFragment.wxs [You may use/skip -sreg, -sfrag, -dr, -var according to your need] *Candle it* %WIX%/bin/candle.exe -dPluginProjectDir=%WORKING%\..\exe\plugin ..\Fragments\pluginFilesFragment.wxs *In setup.wxs add* Feature Id=PluginFeature Title=MySetup Level=1 ComponentGroupRef Id=pluginFiles / /Feature *Light it to build msi* %WIX%/bin/light.exe -o ..\wix-setups\setup setup.wixobj pluginFilesFragment.wixobj -ext WixUtilExtension -ext WixUIExtension -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-exe-tp7583483p7583536.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Heat.exe
Hi I am new to WIX, Can any one help me in pointing the heat.exe. Does it comes with WiX tool? And what are the steps or Command to run the Heat.EXE. Thanks in advance. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-exe-tp7583483.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe
Run heat.exe /? at a cmd prompt this will list all the parameters Steve -Original Message- From: chennam [mailto:chatrapathi.chen...@gmail.com] Sent: February-11-13 4:33 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Heat.exe Hi I am new to WIX, Can any one help me in pointing the heat.exe. Does it comes with WiX tool? And what are the steps or Command to run the Heat.EXE. Thanks in advance. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-exe-tp7583483.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe
Thanks Steve, Intially cmd was notable to recognize Heat.exe as internal or external cmd. Now was able to fingure out heat.exe from Wixtool bin. After harvesting the with Heat.exe a fragment file of .WXS is generated based on the file structure of web application.But I was thinking the MSI file should also be generated when we run heat command as pre build event of Installer setup project. Not sure I am right or wrong ;Can you please say when does the MSI gets created? Thanks in advance. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-exe-tp7583483p7583485.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Heat.exe, suppress COM usage (-scom)
I'm harvesting a directory/file structure. I do not want COM visible files to be COM registered - this is for a server-side product that doesn't use registry-based COM. Some of the assemblies are COM visible, so heat harvests registry information. I tried adding the suppress COM (-scom) option, but it still harvests COM registration information. It would also be nice if it didn't try to load dependencies while harvesting. I just want directories/files. The heat call I'm making is: heat.exe dir path -dr directoryId -nologo -srd -suid -scom -svb6 -wx -o file I'm curious what the -scom flag is supposed to do. The only documentation I can find is the usage statement suppress COM elements. If I compare with/without, the differences I see are that without the flag there are Class and ProgID elements, but with the flag there are, instead, additional RegistryValue elements that appear to do the same job. Perhaps someone can shed some light on what -scom is intended for? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-exe-suppress-COM-usage-scom-tp7582733.html Sent from the wix-users mailing list archive at Nabble.com. -- Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe, suppress COM usage (-scom)
While it may not be optimal, you could use an XSLT to remove the unwanted elements. If I had to guess, the scom element simply tells heat to use the MSI Registry table instead of the TypeLib (and related) tables. I seem to remember a post by Rob and maybe an ICE saying not to use the TypeLib due to versioning issues. So, if you leave out the scom from the command line, you should be able to write an XSLT to only copy elements if they don't have TypeLib for an element. Untested quick hack to follow: ?xml version=1.0 encoding=utf-8? xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xmlns:msxsl=urn:schemas-microsoft-com:xslt xmlns:wix=http://schemas.microsoft.com/wix/2006/wi; exclude-result-prefixes=msxsl wix xsl:output method=xml indent=yes/ xsl:namespace-alias result-prefix=#default stylesheet-prefix=wix / xsl:template match=@* | node() xsl:copy xsl:apply-templates select=@* | node()/ /xsl:copy /xsl:template xsl:template match=wix:TypeLib /xsl:template /xsl:stylesheet -Original Message- From: JohnB [mailto:john.bu...@telvent.com] Sent: Tuesday, January 08, 2013 2:43 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Heat.exe, suppress COM usage (-scom) I'm harvesting a directory/file structure. I do not want COM visible files to be COM registered - this is for a server-side product that doesn't use registry-based COM. Some of the assemblies are COM visible, so heat harvests registry information. I tried adding the suppress COM (-scom) option, but it still harvests COM registration information. It would also be nice if it didn't try to load dependencies while harvesting. I just want directories/files. The heat call I'm making is: heat.exe dir path -dr directoryId -nologo -srd -suid -scom -svb6 -wx -o file I'm curious what the -scom flag is supposed to do. The only documentation I can find is the usage statement suppress COM elements. If I compare with/without, the differences I see are that without the flag there are Class and ProgID elements, but with the flag there are, instead, additional RegistryValue elements that appear to do the same job. Perhaps someone can shed some light on what -scom is intended for? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-exe-suppress-COM-usage-scom-tp7582733.html Sent from the wix-users mailing list archive at Nabble.com. -- Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe, suppress COM usage (-scom)
Use -scom -sreg to suppress all COM and registry info if you are only after file information. -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Tuesday, January 08, 2013 4:29 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Heat.exe, suppress COM usage (-scom) While it may not be optimal, you could use an XSLT to remove the unwanted elements. If I had to guess, the scom element simply tells heat to use the MSI Registry table instead of the TypeLib (and related) tables. I seem to remember a post by Rob and maybe an ICE saying not to use the TypeLib due to versioning issues. So, if you leave out the scom from the command line, you should be able to write an XSLT to only copy elements if they don't have TypeLib for an element. Untested quick hack to follow: ?xml version=1.0 encoding=utf-8? xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xmlns:msxsl=urn:schemas-microsoft-com:xslt xmlns:wix=http://schemas.microsoft.com/wix/2006/wi; exclude-result-prefixes=msxsl wix xsl:output method=xml indent=yes/ xsl:namespace-alias result-prefix=#default stylesheet-prefix=wix / xsl:template match=@* | node() xsl:copy xsl:apply-templates select=@* | node()/ /xsl:copy /xsl:template xsl:template match=wix:TypeLib /xsl:template /xsl:stylesheet -Original Message- From: JohnB [mailto:john.bu...@telvent.com] Sent: Tuesday, January 08, 2013 2:43 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Heat.exe, suppress COM usage (-scom) I'm harvesting a directory/file structure. I do not want COM visible files to be COM registered - this is for a server-side product that doesn't use registry-based COM. Some of the assemblies are COM visible, so heat harvests registry information. I tried adding the suppress COM (-scom) option, but it still harvests COM registration information. It would also be nice if it didn't try to load dependencies while harvesting. I just want directories/files. The heat call I'm making is: heat.exe dir path -dr directoryId -nologo -srd -suid -scom -svb6 -wx -o file I'm curious what the -scom flag is supposed to do. The only documentation I can find is the usage statement suppress COM elements. If I compare with/without, the differences I see are that without the flag there are Class and ProgID elements, but with the flag there are, instead, additional RegistryValue elements that appear to do the same job. Perhaps someone can shed some light on what -scom is intended for? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-exe-s uppress-COM-usage-scom-tp7582733.html Sent from the wix-users mailing list archive at Nabble.com. -- Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users --**-- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. -- Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe, suppress COM usage (-scom)
Aha, thanks to Bill, Jacob, and Germano for the suggestions. -scom -sreg seems to do the trick. Regarding the original question, what is -scom useful for? Are there situations where Class and ProgID elements are not desirable? I'm wondering if the usage statement for that flag should be clarified. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-exe-suppress-COM-usage-scom-tp7582733p7582737.html Sent from the wix-users mailing list archive at Nabble.com. -- Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe generate component for files in each folder, not to generate component for each file.
so if the first file in a component exists and is of the correct version
(assuming no other file is marked as the keypath) then Windows Installer
would consider the component state to be present.
What problems can occur with this?
2012/6/21 Alexey Ivanov alexey.iva...@gmail.com:
In the project vacuum-im ~ 1200 files,%)
To fill the Features have to specify 1200 components (if we consider a
1 component is a 1 file)
2012/6/21 Hoover, Jacob jacob.hoo...@greenheck.com:
Since heat allows for a XSLT to be applied to the output anything is
possible but I would highly advise against it. A component is the most
granular part of an installation, so if the first file in a component exists
and is of the correct version (assuming no other file is marked as the
keypath) then Windows Installer would consider the component state to be
present. Is there a reason you don't want to utilize a component per file?
-Original Message-
From: Alexey Ivanov [mailto:alexey.iva...@gmail.com]
Sent: Thursday, June 21, 2012 12:17 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] heat.exe generate component for files in each folder,
not to generate component for each file.
like this
https://github.com/krab/vacuum-im-wix-installer/blob/master/Files.wxs
is possible with wix?
if i run: heat dir install_files -gg -suid -sfrag -srd -out 1.wxs
DirectoryRef Id=TARGETDIR
Component Id=libeay32.dll
Guid={846E7E4B-51A3-4023-AF17-EBC5E0E4AEB6}
File Id=libeay32.dll KeyPath=yes
Source=install_files\libeay32.dll /
/Component
Component Id=libpng15.dll
Guid={3EF0105F-BBA8-4E11-BF71-956403110505}
File Id=libpng15.dll KeyPath=yes
Source=install_files\libpng15.dll /
/Component
Component Id=license.txt
Guid={ADCF4296-AEAE-4451-B55D-5EDA4ADB4CD6}
File Id=license.txt KeyPath=yes
Source=install_files\license.txt /
/Component
Component Id=msvcp100.dll
Guid={64035C09-D6F5-40C3-A008-AF9C73014AA7}
File Id=msvcp100.dll KeyPath=yes
Source=install_files\msvcp100.dll /
/Component
Component Id=msvcr100.dll
Guid={0960591D-EA25-4BB6-B9C8-D622C7A7C5C3}
File Id=msvcr100.dll KeyPath=yes
Source=install_files\msvcr100.dll /
Components for earch file its feature or its msi requirements?
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat
landscape has changed and how IT managers can respond. Discussions will
include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe generate component for files in each folder, not to generate component for each file.
Mostly you will have trouble with small minor updates. If a component is
being updated, only the file designated as the keypath is checked to see if
it is out of date: if it is up to date, all the others are ignored. Those
kind of updates are similar to repairs and repairs are likewise affected.
You'll also have difficulty if you want to add or remove files from each
component. Once released, a component is immutable (in terms of what files
are in it). The only way to update it without breaking component rules would
be to effectively remove and install the a new version of the MSI.
Understanding the component rules is key in Windows Installer and one file
per component makes the component rules easier to work with, which is why it
is the recommendation of many people here.
Windows Installer can handle 1200 components easily. ComponentGroups and
ComponentGroupRefs can simplify managing large numbers of components in the
source code.
-Original Message-
From: Alexey Ivanov [mailto:alexey.iva...@gmail.com]
Sent: 21 June 2012 08:57
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] heat.exe generate component for files in each
folder, not to generate component for each file.
so if the first file in a component exists and is of the correct version
(assuming no other file is marked as the keypath) then Windows Installer
would consider the component state to be present.
What problems can occur with this?
2012/6/21 Alexey Ivanov alexey.iva...@gmail.com:
In the project vacuum-im ~ 1200 files,%)
To fill the Features have to specify 1200 components (if we consider a
1 component is a 1 file)
2012/6/21 Hoover, Jacob jacob.hoo...@greenheck.com:
Since heat allows for a XSLT to be applied to the output anything is
possible but I would highly advise against it. A component is the most
granular part of an installation, so if the first file in a component exists
and is of the correct version (assuming no other file is marked as the
keypath) then Windows Installer would consider the component state to be
present. Is there a reason you don't want to utilize a component per file?
-Original Message-
From: Alexey Ivanov [mailto:alexey.iva...@gmail.com]
Sent: Thursday, June 21, 2012 12:17 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] heat.exe generate component for files in each folder,
not to generate component for each file.
like this
https://github.com/krab/vacuum-im-wix-installer/blob/master/Files.wxs
is possible with wix?
if i run: heat dir install_files -gg -suid -sfrag -srd -out 1.wxs
DirectoryRef Id=TARGETDIR
Component Id=libeay32.dll
Guid={846E7E4B-51A3-4023-AF17-EBC5E0E4AEB6}
File Id=libeay32.dll KeyPath=yes
Source=install_files\libeay32.dll /
/Component
Component Id=libpng15.dll
Guid={3EF0105F-BBA8-4E11-BF71-956403110505}
File Id=libpng15.dll KeyPath=yes
Source=install_files\libpng15.dll /
/Component
Component Id=license.txt
Guid={ADCF4296-AEAE-4451-B55D-5EDA4ADB4CD6}
File Id=license.txt KeyPath=yes
Source=install_files\license.txt /
/Component
Component Id=msvcp100.dll
Guid={64035C09-D6F5-40C3-A008-AF9C73014AA7}
File Id=msvcp100.dll KeyPath=yes
Source=install_files\msvcp100.dll /
/Component
Component Id=msvcr100.dll
Guid={0960591D-EA25-4BB6-B9C8-D622C7A7C5C3}
File Id=msvcr100.dll KeyPath=yes
Source=install_files\msvcr100.dll /
Components for earch file its feature or its msi requirements?
-
-
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond.
Discussions will include endpoint security, mobile security and the
latest in malware threats.
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
-
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond.
Discussions will include endpoint security, mobile security and the
latest in malware threats.
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
-
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat
landscape has changed and how IT managers can respond. Discussions will
include endpoint security, mobile security and the latest
Re: [WiX-users] heat.exe generate component for files in each folder, not to generate component for each file.
Thank you mr. Peter Shirtcliffe!
2012/6/21 Peter Shirtcliffe pshirtcli...@sdl.com:
Mostly you will have trouble with small minor updates. If a component is
being updated, only the file designated as the keypath is checked to see if
it is out of date: if it is up to date, all the others are ignored. Those
kind of updates are similar to repairs and repairs are likewise affected.
You'll also have difficulty if you want to add or remove files from each
component. Once released, a component is immutable (in terms of what files
are in it). The only way to update it without breaking component rules would
be to effectively remove and install the a new version of the MSI.
Understanding the component rules is key in Windows Installer and one file
per component makes the component rules easier to work with, which is why it
is the recommendation of many people here.
Windows Installer can handle 1200 components easily. ComponentGroups and
ComponentGroupRefs can simplify managing large numbers of components in the
source code.
-Original Message-
From: Alexey Ivanov [mailto:alexey.iva...@gmail.com]
Sent: 21 June 2012 08:57
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] heat.exe generate component for files in each
folder, not to generate component for each file.
so if the first file in a component exists and is of the correct version
(assuming no other file is marked as the keypath) then Windows Installer
would consider the component state to be present.
What problems can occur with this?
2012/6/21 Alexey Ivanov alexey.iva...@gmail.com:
In the project vacuum-im ~ 1200 files,%)
To fill the Features have to specify 1200 components (if we consider a
1 component is a 1 file)
2012/6/21 Hoover, Jacob jacob.hoo...@greenheck.com:
Since heat allows for a XSLT to be applied to the output anything is
possible but I would highly advise against it. A component is the most
granular part of an installation, so if the first file in a component exists
and is of the correct version (assuming no other file is marked as the
keypath) then Windows Installer would consider the component state to be
present. Is there a reason you don't want to utilize a component per file?
-Original Message-
From: Alexey Ivanov [mailto:alexey.iva...@gmail.com]
Sent: Thursday, June 21, 2012 12:17 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] heat.exe generate component for files in each folder,
not to generate component for each file.
like this
https://github.com/krab/vacuum-im-wix-installer/blob/master/Files.wxs
is possible with wix?
if i run: heat dir install_files -gg -suid -sfrag -srd -out 1.wxs
DirectoryRef Id=TARGETDIR
Component Id=libeay32.dll
Guid={846E7E4B-51A3-4023-AF17-EBC5E0E4AEB6}
File Id=libeay32.dll KeyPath=yes
Source=install_files\libeay32.dll /
/Component
Component Id=libpng15.dll
Guid={3EF0105F-BBA8-4E11-BF71-956403110505}
File Id=libpng15.dll KeyPath=yes
Source=install_files\libpng15.dll /
/Component
Component Id=license.txt
Guid={ADCF4296-AEAE-4451-B55D-5EDA4ADB4CD6}
File Id=license.txt KeyPath=yes
Source=install_files\license.txt /
/Component
Component Id=msvcp100.dll
Guid={64035C09-D6F5-40C3-A008-AF9C73014AA7}
File Id=msvcp100.dll KeyPath=yes
Source=install_files\msvcp100.dll /
/Component
Component Id=msvcr100.dll
Guid={0960591D-EA25-4BB6-B9C8-D622C7A7C5C3}
File Id=msvcr100.dll KeyPath=yes
Source=install_files\msvcr100.dll /
Components for earch file its feature or its msi requirements?
-
-
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond.
Discussions will include endpoint security, mobile security and the
latest in malware threats.
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
-
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond.
Discussions will include endpoint security, mobile security and the
latest in malware threats.
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
-
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat
landscape has changed
Re: [WiX-users] heat.exe generate component for files in each folder, not to generate component for each file.
Understanding the Component Rules is important:
http://robmensching.com/blog/posts/2003/10/18/Component-Rules-101 :)
On Thu, Jun 21, 2012 at 3:47 PM, Alexey Ivanov alexey.iva...@gmail.comwrote:
Thank you mr. Peter Shirtcliffe!
2012/6/21 Peter Shirtcliffe pshirtcli...@sdl.com:
Mostly you will have trouble with small minor updates. If a component
is
being updated, only the file designated as the keypath is checked to see
if
it is out of date: if it is up to date, all the others are ignored. Those
kind of updates are similar to repairs and repairs are likewise affected.
You'll also have difficulty if you want to add or remove files from each
component. Once released, a component is immutable (in terms of what
files
are in it). The only way to update it without breaking component rules
would
be to effectively remove and install the a new version of the MSI.
Understanding the component rules is key in Windows Installer and one
file
per component makes the component rules easier to work with, which is
why it
is the recommendation of many people here.
Windows Installer can handle 1200 components easily. ComponentGroups and
ComponentGroupRefs can simplify managing large numbers of components in
the
source code.
-Original Message-
From: Alexey Ivanov [mailto:alexey.iva...@gmail.com]
Sent: 21 June 2012 08:57
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] heat.exe generate component for files in each
folder, not to generate component for each file.
so if the first file in a component exists and is of the correct version
(assuming no other file is marked as the keypath) then Windows Installer
would consider the component state to be present.
What problems can occur with this?
2012/6/21 Alexey Ivanov alexey.iva...@gmail.com:
In the project vacuum-im ~ 1200 files,%)
To fill the Features have to specify 1200 components (if we consider a
1 component is a 1 file)
2012/6/21 Hoover, Jacob jacob.hoo...@greenheck.com:
Since heat allows for a XSLT to be applied to the output anything is
possible but I would highly advise against it. A component is the most
granular part of an installation, so if the first file in a component
exists
and is of the correct version (assuming no other file is marked as the
keypath) then Windows Installer would consider the component state to be
present. Is there a reason you don't want to utilize a component per
file?
-Original Message-
From: Alexey Ivanov [mailto:alexey.iva...@gmail.com]
Sent: Thursday, June 21, 2012 12:17 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] heat.exe generate component for files in each
folder,
not to generate component for each file.
like this
https://github.com/krab/vacuum-im-wix-installer/blob/master/Files.wxs
is possible with wix?
if i run: heat dir install_files -gg -suid -sfrag -srd -out 1.wxs
DirectoryRef Id=TARGETDIR
Component Id=libeay32.dll
Guid={846E7E4B-51A3-4023-AF17-EBC5E0E4AEB6}
File Id=libeay32.dll KeyPath=yes
Source=install_files\libeay32.dll /
/Component
Component Id=libpng15.dll
Guid={3EF0105F-BBA8-4E11-BF71-956403110505}
File Id=libpng15.dll KeyPath=yes
Source=install_files\libpng15.dll /
/Component
Component Id=license.txt
Guid={ADCF4296-AEAE-4451-B55D-5EDA4ADB4CD6}
File Id=license.txt KeyPath=yes
Source=install_files\license.txt /
/Component
Component Id=msvcp100.dll
Guid={64035C09-D6F5-40C3-A008-AF9C73014AA7}
File Id=msvcp100.dll KeyPath=yes
Source=install_files\msvcp100.dll /
/Component
Component Id=msvcr100.dll
Guid={0960591D-EA25-4BB6-B9C8-D622C7A7C5C3}
File Id=msvcr100.dll KeyPath=yes
Source=install_files\msvcr100.dll /
Components for earch file its feature or its msi requirements?
-
-
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond.
Discussions will include endpoint security, mobile security and the
latest in malware threats.
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
-
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond.
Discussions will include endpoint security, mobile security and the
latest in malware threats.
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users
[WiX-users] heat.exe generate component for files in each folder, not to generate component for each file.
like this https://github.com/krab/vacuum-im-wix-installer/blob/master/Files.wxs
is possible with wix?
if i run: heat dir install_files -gg -suid -sfrag -srd -out 1.wxs
DirectoryRef Id=TARGETDIR
Component Id=libeay32.dll
Guid={846E7E4B-51A3-4023-AF17-EBC5E0E4AEB6}
File Id=libeay32.dll KeyPath=yes
Source=install_files\libeay32.dll /
/Component
Component Id=libpng15.dll
Guid={3EF0105F-BBA8-4E11-BF71-956403110505}
File Id=libpng15.dll KeyPath=yes
Source=install_files\libpng15.dll /
/Component
Component Id=license.txt Guid={ADCF4296-AEAE-4451-B55D-5EDA4ADB4CD6}
File Id=license.txt KeyPath=yes
Source=install_files\license.txt /
/Component
Component Id=msvcp100.dll
Guid={64035C09-D6F5-40C3-A008-AF9C73014AA7}
File Id=msvcp100.dll KeyPath=yes
Source=install_files\msvcp100.dll /
/Component
Component Id=msvcr100.dll
Guid={0960591D-EA25-4BB6-B9C8-D622C7A7C5C3}
File Id=msvcr100.dll KeyPath=yes
Source=install_files\msvcr100.dll /
Components for earch file its feature or its msi requirements?
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe generate component for files in each folder, not to generate component for each file.
Since heat allows for a XSLT to be applied to the output anything is possible
but I would highly advise against it. A component is the most granular part of
an installation, so if the first file in a component exists and is of the
correct version (assuming no other file is marked as the keypath) then Windows
Installer would consider the component state to be present. Is there a reason
you don't want to utilize a component per file?
-Original Message-
From: Alexey Ivanov [mailto:alexey.iva...@gmail.com]
Sent: Thursday, June 21, 2012 12:17 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] heat.exe generate component for files in each folder, not
to generate component for each file.
like this https://github.com/krab/vacuum-im-wix-installer/blob/master/Files.wxs
is possible with wix?
if i run: heat dir install_files -gg -suid -sfrag -srd -out 1.wxs
DirectoryRef Id=TARGETDIR
Component Id=libeay32.dll
Guid={846E7E4B-51A3-4023-AF17-EBC5E0E4AEB6}
File Id=libeay32.dll KeyPath=yes
Source=install_files\libeay32.dll /
/Component
Component Id=libpng15.dll
Guid={3EF0105F-BBA8-4E11-BF71-956403110505}
File Id=libpng15.dll KeyPath=yes
Source=install_files\libpng15.dll /
/Component
Component Id=license.txt Guid={ADCF4296-AEAE-4451-B55D-5EDA4ADB4CD6}
File Id=license.txt KeyPath=yes
Source=install_files\license.txt /
/Component
Component Id=msvcp100.dll
Guid={64035C09-D6F5-40C3-A008-AF9C73014AA7}
File Id=msvcp100.dll KeyPath=yes
Source=install_files\msvcp100.dll /
/Component
Component Id=msvcr100.dll
Guid={0960591D-EA25-4BB6-B9C8-D622C7A7C5C3}
File Id=msvcr100.dll KeyPath=yes
Source=install_files\msvcr100.dll /
Components for earch file its feature or its msi requirements?
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat
landscape has changed and how IT managers can respond. Discussions will include
endpoint security, mobile security and the latest in malware threats.
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe generate component for files in each folder, not to generate component for each file.
In the project vacuum-im ~ 1200 files,%)
To fill the Features have to specify 1200 components (if we consider a
1 component is a 1 file)
2012/6/21 Hoover, Jacob jacob.hoo...@greenheck.com:
Since heat allows for a XSLT to be applied to the output anything is
possible but I would highly advise against it. A component is the most
granular part of an installation, so if the first file in a component exists
and is of the correct version (assuming no other file is marked as the
keypath) then Windows Installer would consider the component state to be
present. Is there a reason you don't want to utilize a component per file?
-Original Message-
From: Alexey Ivanov [mailto:alexey.iva...@gmail.com]
Sent: Thursday, June 21, 2012 12:17 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] heat.exe generate component for files in each folder,
not to generate component for each file.
like this
https://github.com/krab/vacuum-im-wix-installer/blob/master/Files.wxs
is possible with wix?
if i run: heat dir install_files -gg -suid -sfrag -srd -out 1.wxs
DirectoryRef Id=TARGETDIR
Component Id=libeay32.dll
Guid={846E7E4B-51A3-4023-AF17-EBC5E0E4AEB6}
File Id=libeay32.dll KeyPath=yes
Source=install_files\libeay32.dll /
/Component
Component Id=libpng15.dll
Guid={3EF0105F-BBA8-4E11-BF71-956403110505}
File Id=libpng15.dll KeyPath=yes
Source=install_files\libpng15.dll /
/Component
Component Id=license.txt
Guid={ADCF4296-AEAE-4451-B55D-5EDA4ADB4CD6}
File Id=license.txt KeyPath=yes
Source=install_files\license.txt /
/Component
Component Id=msvcp100.dll
Guid={64035C09-D6F5-40C3-A008-AF9C73014AA7}
File Id=msvcp100.dll KeyPath=yes
Source=install_files\msvcp100.dll /
/Component
Component Id=msvcr100.dll
Guid={0960591D-EA25-4BB6-B9C8-D622C7A7C5C3}
File Id=msvcr100.dll KeyPath=yes
Source=install_files\msvcr100.dll /
Components for earch file its feature or its msi requirements?
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat
landscape has changed and how IT managers can respond. Discussions will
include endpoint security, mobile security and the latest in malware threats.
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] heat.exe(0,0): error HEAT5307: Build failed.
Hi All, I've just reinstalled a new laptop with VS2008, Wix3.5 but now when I try build my projects the setup projects fail to build with the following error: heat.exe(0,0): error HEAT5307: Build failed. All the links I see on the internet refer to C++ projects. These however are C# projects. It feels like I must be missing something? Perhaps a patch? I'm running Windows 7 Home Premium on a Core i7 with 8G ram. Thanks, Peter --- Peter Solomon -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version
Thanks a lot for these details! Taking your Manufacturer xsl as a baseline example, I tried to replace the Name attribute in Product but really made no progress. I got this crappy code to work, but would like something like this. xsl:template match=packa...@name xsl:attribute name=Name$(var.ProductName)/xsl:attribute /xsl:template I got this to work, but I do not like checking for 'PUT-PRODUCT-NAME-HERE' constant. xsl:template match=@Name[.='PUT-PRODUCT-NAME-HERE'] xsl:attribute name=Name$(var.ProductName)/xsl:attribute /xsl:template Also, I want to insert an attribute in the Package element, and this code again does not work. xsl:template match=Package xsl:attribute name=Id$(var.PackageId)/xsl:attribute /xsl:template Any idea what I am missing here? I should confess, this is the first time I am writing an Xsl transform. thanks, sangeeta On Thu, Dec 9, 2010 at 2:00 PM, Edwin G. Castro [via Windows Installer XML (WiX) toolset] ml-node+5820142-512686066-306...@n2.nabble.comml-node%2b5820142-512686066-306...@n2.nabble.com wrote: Here are your options: 1.) Use a XLST transform to change the generated wxs 2.) Use -var to specify a preprocessor variable (such as var.MySource) and specify the value for MySource on the command line to candle.exe (see the -d switch) 3.) Specify a base path when calling light.exe (see the -b switch) Option three is interesting because you don't use the -var parameter to heat.exe at all. Instead you tell light.exe to use one or more base paths as the roots to look for files (you can specify more than one). Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: sangeeta1 [mailto:[hidden email]http://user/SendEmail.jtp?type=nodenode=5820142i=0] Sent: Wednesday, December 08, 2010 8:47 PM To: [hidden email]http://user/SendEmail.jtp?type=nodenode=5820142i=1 Subject: Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version After trying out an example, I see the significance of the -var variable. Regarding you example in using -var How can I replace the value of Source to a physical path of the root folder (like c:\temp\test) without having to use a wix variable var.MySource? I am automating the generation of msi given a set of installable files. I will be invoking these commands from .net program. many thanks for your help on this.. On Wed, Dec 8, 2010 at 5:01 PM, Edwin G. Castro [via Windows Installer XML (WiX) toolset] [hidden email]http://user/SendEmail.jtp?type=nodenode=5820142i=2ml- [hidden email] http://user/SendEmail.jtp?type=nodenode=5820142i=3 wrote: Heat does not generate a Product/ element. Heat /? shows the following documentation for -var: -var VariableName substitute File/@Source=SourceDir with a preprocessor or a wix variable (e.g. -var var.MySource will become File/@Source=$(var.MySource)\myfile.txt and -var wix.MySource will become File/@Source=!(wix.MySource)\myfile.txt This does text transformation on the generated output wxs file. I created an empty text file called test.txt and used the following command line to harvest it using heat.exe: heat file test.txt -out test.wxs Here are the contents of test.wxs: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment DirectoryRef Id=TARGETDIR Directory Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Name=code / /DirectoryRef /Fragment Fragment DirectoryRef Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Component Id=cmp5BA64E6B74419477D4B75A1E802397FC Guid=PUT-GUID-HERE File Id=fil67D465DE6C69EA3B3CD0B7487E6132B6 KeyPath=yes Source=SourceDir\code\test.txt / /Component /DirectoryRef /Fragment /Wix Notice that File/@Source=SourceDir\code\test.txt If use -var like this: heat file test.txt -out test.wxs -var var.CodeDir Then I get this: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment DirectoryRef Id=TARGETDIR Directory Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Name=code / /DirectoryRef /Fragment Fragment DirectoryRef Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Component Id=cmp5BA64E6B74419477D4B75A1E802397FC Guid=PUT-GUID-HERE File Id=fil67D465DE6C69EA3B3CD0B7487E6132B6 KeyPath=yes Source=$(var.CodeDir)\code\test.txt / /Component /DirectoryRef /Fragment /Wix Notice that File/@Source=$(var.CodeDir)\code\test.txt just like the documentation
Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version
Add xmlns:wix=http://schemas.microsoft.com/wix/2006/wi; in the root element of your XSLT and change your template to: xsl:template match=wix:packa...@name xsl:attribute name=Name$(var.ProductName)/xsl:attribute /xsl:template -Original Message- From: sangeeta1 [mailto:snmsn...@gmail.com] Sent: Friday, December 10, 2010 9:38 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version Thanks a lot for these details! Taking your Manufacturer xsl as a baseline example, I tried to replace the Name attribute in Product but really made no progress. I got this crappy code to work, but would like something like this. xsl:template match=packa...@name xsl:attribute name=Name$(var.ProductName)/xsl:attribute /xsl:template I got this to work, but I do not like checking for 'PUT-PRODUCT-NAME-HERE' constant. xsl:template match=@Name[.='PUT-PRODUCT-NAME-HERE'] xsl:attribute name=Name$(var.ProductName)/xsl:attribute /xsl:template Also, I want to insert an attribute in the Package element, and this code again does not work. xsl:template match=Package xsl:attribute name=Id$(var.PackageId)/xsl:attribute /xsl:template Any idea what I am missing here? I should confess, this is the first time I am writing an Xsl transform. thanks, sangeeta On Thu, Dec 9, 2010 at 2:00 PM, Edwin G. Castro [via Windows Installer XML (WiX) toolset] ml-node+5820142-512686066-306...@n2.nabble.comml-node%2b5820142-512686066-306...@n2.nabble.com wrote: Here are your options: 1.) Use a XLST transform to change the generated wxs 2.) Use -var to specify a preprocessor variable (such as var.MySource) and specify the value for MySource on the command line to candle.exe (see the -d switch) 3.) Specify a base path when calling light.exe (see the -b switch) Option three is interesting because you don't use the -var parameter to heat.exe at all. Instead you tell light.exe to use one or more base paths as the roots to look for files (you can specify more than one). Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: sangeeta1 [mailto:[hidden email]http://user/SendEmail.jtp?type=nodenode=5820142i=0] Sent: Wednesday, December 08, 2010 8:47 PM To: [hidden email]http://user/SendEmail.jtp?type=nodenode=5820142i=1 Subject: Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version After trying out an example, I see the significance of the -var variable. Regarding you example in using -var How can I replace the value of Source to a physical path of the root folder (like c:\temp\test) without having to use a wix variable var.MySource? I am automating the generation of msi given a set of installable files. I will be invoking these commands from .net program. many thanks for your help on this.. On Wed, Dec 8, 2010 at 5:01 PM, Edwin G. Castro [via Windows Installer XML (WiX) toolset] [hidden email]http://user/SendEmail.jtp?type=nodenode=5820142i=2ml- [hidden email] http://user/SendEmail.jtp?type=nodenode=5820142i=3 wrote: Heat does not generate a Product/ element. Heat /? shows the following documentation for -var: -var VariableName substitute File/@Source=SourceDir with a preprocessor or a wix variable (e.g. -var var.MySource will become File/@Source=$(var.MySource)\myfile.txt and -var wix.MySource will become File/@Source=!(wix.MySource)\myfile.txt This does text transformation on the generated output wxs file. I created an empty text file called test.txt and used the following command line to harvest it using heat.exe: heat file test.txt -out test.wxs Here are the contents of test.wxs: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment DirectoryRef Id=TARGETDIR Directory Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Name=code / /DirectoryRef /Fragment Fragment DirectoryRef Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Component Id=cmp5BA64E6B74419477D4B75A1E802397FC Guid=PUT-GUID-HERE File Id=fil67D465DE6C69EA3B3CD0B7487E6132B6 KeyPath=yes Source=SourceDir\code\test.txt / /Component /DirectoryRef /Fragment /Wix Notice that File/@Source=SourceDir\code\test.txt If use -var like this: heat file test.txt -out test.wxs -var var.CodeDir Then I get this: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment DirectoryRef Id=TARGETDIR Directory Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Name=code
Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version
The Wix schema does not let me add a attribute to Package though. I want to assign a package Id to the msi. xsl:template match=wix:Package xsl:attribute name=Id$(var.PackageId)/xsl:attribute /xsl:template With you example, I am able to edit the Product name. thanks. xsl:template match=wix:Product/@Name xsl:attribute name=Name$(var.ProductNameName)/xsl:attribute /xsl:template On Fri, Dec 10, 2010 at 12:55 PM, Blair-2 [via Windows Installer XML (WiX) toolset] ml-node+5824029-456030519-306...@n2.nabble.comml-node%2b5824029-456030519-306...@n2.nabble.com wrote: Add xmlns:wix=http://schemas.microsoft.com/wix/2006/wi; in the root element of your XSLT and change your template to: xsl:template match=wix:packa...@name xsl:attribute name=Name$(var.ProductName)/xsl:attribute /xsl:template -Original Message- From: sangeeta1 [mailto:[hidden email]http://user/SendEmail.jtp?type=nodenode=5824029i=0] Sent: Friday, December 10, 2010 9:38 AM To: [hidden email] http://user/SendEmail.jtp?type=nodenode=5824029i=1 Subject: Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version Thanks a lot for these details! Taking your Manufacturer xsl as a baseline example, I tried to replace the Name attribute in Product but really made no progress. I got this crappy code to work, but would like something like this. xsl:template match=packa...@name xsl:attribute name=Name$(var.ProductName)/xsl:attribute /xsl:template I got this to work, but I do not like checking for 'PUT-PRODUCT-NAME-HERE' constant. xsl:template match=@Name[.='PUT-PRODUCT-NAME-HERE'] xsl:attribute name=Name$(var.ProductName)/xsl:attribute /xsl:template Also, I want to insert an attribute in the Package element, and this code again does not work. xsl:template match=Package xsl:attribute name=Id$(var.PackageId)/xsl:attribute /xsl:template Any idea what I am missing here? I should confess, this is the first time I am writing an Xsl transform. thanks, sangeeta On Thu, Dec 9, 2010 at 2:00 PM, Edwin G. Castro [via Windows Installer XML (WiX) toolset] [hidden email]http://user/SendEmail.jtp?type=nodenode=5824029i=2 [hidden email] http://user/SendEmail.jtp?type=nodenode=5824029i=3 wrote: Here are your options: 1.) Use a XLST transform to change the generated wxs 2.) Use -var to specify a preprocessor variable (such as var.MySource) and specify the value for MySource on the command line to candle.exe (see the -d switch) 3.) Specify a base path when calling light.exe (see the -b switch) Option three is interesting because you don't use the -var parameter to heat.exe at all. Instead you tell light.exe to use one or more base paths as the roots to look for files (you can specify more than one). Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: sangeeta1 [mailto:[hidden email] http://user/SendEmail.jtp?type=nodenode=5820142i=0] Sent: Wednesday, December 08, 2010 8:47 PM To: [hidden email] http://user/SendEmail.jtp?type=nodenode=5820142i=1 Subject: Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version After trying out an example, I see the significance of the -var variable. Regarding you example in using -var How can I replace the value of Source to a physical path of the root folder (like c:\temp\test) without having to use a wix variable var.MySource? I am automating the generation of msi given a set of installable files. I will be invoking these commands from .net program. many thanks for your help on this.. On Wed, Dec 8, 2010 at 5:01 PM, Edwin G. Castro [via Windows Installer XML (WiX) toolset] [hidden email] http://user/SendEmail.jtp?type=nodenode=5820142i=2ml- [hidden email] http://user/SendEmail.jtp?type=nodenode=5820142i=3 wrote: Heat does not generate a Product/ element. Heat /? shows the following documentation for -var: -var VariableName substitute File/@Source=SourceDir with a preprocessor or a wix variable (e.g. -var var.MySource will become File/@Source=$(var.MySource)\myfile.txt and -var wix.MySource will become File/@Source=!(wix.MySource)\myfile.txt This does text transformation on the generated output wxs file. I created an empty text file called test.txt and used the following command line to harvest it using heat.exe: heat file test.txt -out test.wxs Here are the contents of test.wxs: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment DirectoryRef Id=TARGETDIR Directory Id
Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version
xsl:template match=wix:Package Will match the Package element itself. You'll need to copy the element, *then* add the attribute to the copied element. xsl:template match=wix:Package xsl:copy xsl:apply-templates select=@*/ xsl:attribute name=Id$(var.PackageId)/xsl:attribute /xsl:copy /xsl:template A couple of comments: 1.) Consider reading Learning XSLT and XSLT Cookbook. Great books! 2.) Consider *not* setting Package/@Id. You should let WiX generate a new Package/@Id on every build of your package as per the Windows Installer documentation. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: sangeeta1 [mailto:snmsn...@gmail.com] Sent: Friday, December 10, 2010 10:18 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version The Wix schema does not let me add a attribute to Package though. I want to assign a package Id to the msi. xsl:template match=wix:Package xsl:attribute name=Id$(var.PackageId)/xsl:attribute /xsl:template With you example, I am able to edit the Product name. thanks. xsl:template match=wix:Product/@Name xsl:attribute name=Name$(var.ProductNameName)/xsl:attribute /xsl:template On Fri, Dec 10, 2010 at 12:55 PM, Blair-2 [via Windows Installer XML (WiX) toolset] ml-node+5824029-456030519-306...@n2.nabble.comml- node%2b5824029-456030519-306...@n2.nabble.com wrote: Add xmlns:wix=http://schemas.microsoft.com/wix/2006/wi; in the root element of your XSLT and change your template to: xsl:template match=wix:packa...@name xsl:attribute name=Name$(var.ProductName)/xsl:attribute /xsl:template -Original Message- From: sangeeta1 [mailto:[hidden email]http://user/SendEmail.jtp?type=nodenode=5824029i=0] Sent: Friday, December 10, 2010 9:38 AM To: [hidden email] http://user/SendEmail.jtp?type=nodenode=5824029i=1 Subject: Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version Thanks a lot for these details! Taking your Manufacturer xsl as a baseline example, I tried to replace the Name attribute in Product but really made no progress. I got this crappy code to work, but would like something like this. xsl:template match=packa...@name xsl:attribute name=Name$(var.ProductName)/xsl:attribute /xsl:template I got this to work, but I do not like checking for 'PUT-PRODUCT-NAME- HERE' constant. xsl:template match=@Name[.='PUT-PRODUCT-NAME-HERE'] xsl:attribute name=Name$(var.ProductName)/xsl:attribute /xsl:template Also, I want to insert an attribute in the Package element, and this code again does not work. xsl:template match=Package xsl:attribute name=Id$(var.PackageId)/xsl:attribute /xsl:template Any idea what I am missing here? I should confess, this is the first time I am writing an Xsl transform. thanks, sangeeta On Thu, Dec 9, 2010 at 2:00 PM, Edwin G. Castro [via Windows Installer XML (WiX) toolset] [hidden email]http://user/SendEmail.jtp?type=nodenode=5824029i=2 [hidden email] http://user/SendEmail.jtp?type=nodenode=5824029i=3 wrote: Here are your options: 1.) Use a XLST transform to change the generated wxs 2.) Use -var to specify a preprocessor variable (such as var.MySource) and specify the value for MySource on the command line to candle.exe (see the -d switch) 3.) Specify a base path when calling light.exe (see the -b switch) Option three is interesting because you don't use the -var parameter to heat.exe at all. Instead you tell light.exe to use one or more base paths as the roots to look for files (you can specify more than one). Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: sangeeta1 [mailto:[hidden email] http://user/SendEmail.jtp?type=nodenode=5820142i=0] Sent: Wednesday, December 08, 2010 8:47 PM To: [hidden email] http://user/SendEmail.jtp?type=nodenode=5820142i=1 Subject: Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version After trying out an example, I see the significance of the -var variable. Regarding you example in using -var How can I replace the value of Source to a physical path of the root folder (like c:\temp\test) without having to use a wix variable var.MySource? I am automating the generation of msi given a set of installable files. I
Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version
The source .wxs file that Heat.exe generates, does not contain Package Id. I was therefore thinking of passing a new Guid every time the tool is run. Is there any way Heat.exe can set Package Id in the .wxs file? Thanks for the list of reference books. On Fri, Dec 10, 2010 at 2:01 PM, Edwin G. Castro [via Windows Installer XML (WiX) toolset] ml-node+5824258-1220359716-306...@n2.nabble.comml-node%2b5824258-1220359716-306...@n2.nabble.com wrote: xsl:template match=wix:Package Will match the Package element itself. You'll need to copy the element, *then* add the attribute to the copied element. xsl:template match=wix:Package xsl:copy xsl:apply-templates select=@*/ xsl:attribute name=Id$(var.PackageId)/xsl:attribute /xsl:copy /xsl:template A couple of comments: 1.) Consider reading Learning XSLT and XSLT Cookbook. Great books! 2.) Consider *not* setting Package/@Id. You should let WiX generate a new Package/@Id on every build of your package as per the Windows Installer documentation. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: sangeeta1 [mailto:[hidden email]http://user/SendEmail.jtp?type=nodenode=5824258i=0] Sent: Friday, December 10, 2010 10:18 AM To: [hidden email]http://user/SendEmail.jtp?type=nodenode=5824258i=1 Subject: Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version The Wix schema does not let me add a attribute to Package though. I want to assign a package Id to the msi. xsl:template match=wix:Package xsl:attribute name=Id$(var.PackageId)/xsl:attribute /xsl:template With you example, I am able to edit the Product name. thanks. xsl:template match=wix:Product/@Name xsl:attribute name=Name$(var.ProductNameName)/xsl:attribute /xsl:template On Fri, Dec 10, 2010 at 12:55 PM, Blair-2 [via Windows Installer XML (WiX) toolset] [hidden email]http://user/SendEmail.jtp?type=nodenode=5824258i=2ml- [hidden email] http://user/SendEmail.jtp?type=nodenode=5824258i=3 wrote: Add xmlns:wix=http://schemas.microsoft.com/wix/2006/wi; in the root element of your XSLT and change your template to: xsl:template match=wix:packa...@name xsl:attribute name=Name$(var.ProductName)/xsl:attribute /xsl:template -Original Message- From: sangeeta1 [mailto:[hidden email]http://user/SendEmail.jtp?type=nodenode=5824029i=0] Sent: Friday, December 10, 2010 9:38 AM To: [hidden email] http://user/SendEmail.jtp?type=nodenode=5824029i=1 Subject: Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version Thanks a lot for these details! Taking your Manufacturer xsl as a baseline example, I tried to replace the Name attribute in Product but really made no progress. I got this crappy code to work, but would like something like this. xsl:template match=packa...@name xsl:attribute name=Name$(var.ProductName)/xsl:attribute /xsl:template I got this to work, but I do not like checking for 'PUT-PRODUCT-NAME- HERE' constant. xsl:template match=@Name[.='PUT-PRODUCT-NAME-HERE'] xsl:attribute name=Name$(var.ProductName)/xsl:attribute /xsl:template Also, I want to insert an attribute in the Package element, and this code again does not work. xsl:template match=Package xsl:attribute name=Id$(var.PackageId)/xsl:attribute /xsl:template Any idea what I am missing here? I should confess, this is the first time I am writing an Xsl transform. thanks, sangeeta On Thu, Dec 9, 2010 at 2:00 PM, Edwin G. Castro [via Windows Installer XML (WiX) toolset] [hidden email]http://user/SendEmail.jtp?type=nodenode=5824029i=2 [hidden email] http://user/SendEmail.jtp?type=nodenode=5824029i=3 wrote: Here are your options: 1.) Use a XLST transform to change the generated wxs 2.) Use -var to specify a preprocessor variable (such as var.MySource) and specify the value for MySource on the command line to candle.exe (see the -d switch) 3.) Specify a base path when calling light.exe (see the -b switch) Option three is interesting because you don't use the -var parameter to heat.exe at all. Instead you tell light.exe to use one or more base paths as the roots to look for files (you can specify more than one). Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: sangeeta1
Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version
Heat.exe doesn't need to set Package/@Id at all. Candle.exe will set Package/@Id at compile-time to a new Guid if one is not specified in the .wxs file. My recommendation is to not add your own Guid with a XSLT transform and to let candle.exe perform it's default action concerning Package/@Id. From http://wix.sourceforge.net/manual-wix3/wix_xsd_package.htm Description for Id attribute: The package code GUID for a product or merge module. When compiling a product, this attribute should not be set in order to allow the package code to be generated for each build. When compiling a merge module, this attribute must be set to the modularization guid. WiX tries to do the right thing for you by default but will let you do whatever you want. In other words, if it's not required, then you probably don't need to set it. Only set non-required attributes when you determine via testing and documentation that you really need it. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: sangeeta1 [mailto:snmsn...@gmail.com] Sent: Friday, December 10, 2010 11:11 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version The source .wxs file that Heat.exe generates, does not contain Package Id. I was therefore thinking of passing a new Guid every time the tool is run. Is there any way Heat.exe can set Package Id in the .wxs file? Thanks for the list of reference books. On Fri, Dec 10, 2010 at 2:01 PM, Edwin G. Castro [via Windows Installer XML (WiX) toolset] ml-node+5824258-1220359716-306...@n2.nabble.comml- node%2b5824258-1220359716-306...@n2.nabble.com wrote: xsl:template match=wix:Package Will match the Package element itself. You'll need to copy the element, *then* add the attribute to the copied element. xsl:template match=wix:Package xsl:copy xsl:apply-templates select=@*/ xsl:attribute name=Id$(var.PackageId)/xsl:attribute /xsl:copy /xsl:template A couple of comments: 1.) Consider reading Learning XSLT and XSLT Cookbook. Great books! 2.) Consider *not* setting Package/@Id. You should let WiX generate a new Package/@Id on every build of your package as per the Windows Installer documentation. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: sangeeta1 [mailto:[hidden email]http://user/SendEmail.jtp?type=nodenode=5824258i=0] Sent: Friday, December 10, 2010 10:18 AM To: [hidden email]http://user/SendEmail.jtp?type=nodenode=5824258i=1 Subject: Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version The Wix schema does not let me add a attribute to Package though. I want to assign a package Id to the msi. xsl:template match=wix:Package xsl:attribute name=Id$(var.PackageId)/xsl:attribute /xsl:template With you example, I am able to edit the Product name. thanks. xsl:template match=wix:Product/@Name xsl:attribute name=Name$(var.ProductNameName)/xsl:attribute /xsl:template On Fri, Dec 10, 2010 at 12:55 PM, Blair-2 [via Windows Installer XML (WiX) toolset] [hidden email]http://user/SendEmail.jtp?type=nodenode=5824258i=2ml- [hidden email] http://user/SendEmail.jtp?type=nodenode=5824258i=3 wrote: Add xmlns:wix=http://schemas.microsoft.com/wix/2006/wi; in the root element of your XSLT and change your template to: xsl:template match=wix:packa...@name xsl:attribute name=Name$(var.ProductName)/xsl:attribute /xsl:template -Original Message- From: sangeeta1 [mailto:[hidden email]http://user/SendEmail.jtp?type=nodenode=5824029i=0] Sent: Friday, December 10, 2010 9:38 AM To: [hidden email] http://user/SendEmail.jtp?type=nodenode=5824029i=1 Subject: Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version Thanks a lot for these details! Taking your Manufacturer xsl as a baseline example, I tried to replace the Name attribute in Product but really made no progress. I got this crappy code to work, but would like something like this. xsl:template match=packa...@name xsl:attribute name=Name$(var.ProductName)/xsl:attribute /xsl:template I got this to work, but I do not like checking for 'PUT-PRODUCT-NAME- HERE' constant. xsl:template match=@Name[.='PUT-PRODUCT-NAME-HERE'] xsl:attribute name=Name$(var.ProductName)/xsl:attribute /xsl:template
Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version
Here are your options: 1.) Use a XLST transform to change the generated wxs 2.) Use -var to specify a preprocessor variable (such as var.MySource) and specify the value for MySource on the command line to candle.exe (see the -d switch) 3.) Specify a base path when calling light.exe (see the -b switch) Option three is interesting because you don't use the -var parameter to heat.exe at all. Instead you tell light.exe to use one or more base paths as the roots to look for files (you can specify more than one). Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: sangeeta1 [mailto:snmsn...@gmail.com] Sent: Wednesday, December 08, 2010 8:47 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version After trying out an example, I see the significance of the -var variable. Regarding you example in using -var How can I replace the value of Source to a physical path of the root folder (like c:\temp\test) without having to use a wix variable var.MySource? I am automating the generation of msi given a set of installable files. I will be invoking these commands from .net program. many thanks for your help on this.. On Wed, Dec 8, 2010 at 5:01 PM, Edwin G. Castro [via Windows Installer XML (WiX) toolset] ml-node+5816953-1419466290-306...@n2.nabble.comml- node%2b5816953-1419466290-306...@n2.nabble.com wrote: Heat does not generate a Product/ element. Heat /? shows the following documentation for -var: -var VariableName substitute File/@Source=SourceDir with a preprocessor or a wix variable (e.g. -var var.MySource will become File/@Source=$(var.MySource)\myfile.txt and -var wix.MySource will become File/@Source=!(wix.MySource)\myfile.txt This does text transformation on the generated output wxs file. I created an empty text file called test.txt and used the following command line to harvest it using heat.exe: heat file test.txt -out test.wxs Here are the contents of test.wxs: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment DirectoryRef Id=TARGETDIR Directory Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Name=code / /DirectoryRef /Fragment Fragment DirectoryRef Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Component Id=cmp5BA64E6B74419477D4B75A1E802397FC Guid=PUT-GUID-HERE File Id=fil67D465DE6C69EA3B3CD0B7487E6132B6 KeyPath=yes Source=SourceDir\code\test.txt / /Component /DirectoryRef /Fragment /Wix Notice that File/@Source=SourceDir\code\test.txt If use -var like this: heat file test.txt -out test.wxs -var var.CodeDir Then I get this: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment DirectoryRef Id=TARGETDIR Directory Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Name=code / /DirectoryRef /Fragment Fragment DirectoryRef Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Component Id=cmp5BA64E6B74419477D4B75A1E802397FC Guid=PUT-GUID-HERE File Id=fil67D465DE6C69EA3B3CD0B7487E6132B6 KeyPath=yes Source=$(var.CodeDir)\code\test.txt / /Component /DirectoryRef /Fragment /Wix Notice that File/@Source=$(var.CodeDir)\code\test.txt just like the documentation says. In a Product/ element is *not* generated in either example. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: sangeeta1 [mailto:[hidden email]http://user/SendEmail.jtp?type=nodenode=5816953i=0] Sent: Wednesday, December 08, 2010 12:25 PM To: [hidden email]http://user/SendEmail.jtp?type=nodenode=5816953i=1 Subject: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version Hi all, I am trying to generate a wxs source file using Heat.exe and wanted to check if I can pass values for Manufacturer, Name, Title and version to heat.exe? I tried using -var argument, but does nt seem to update it to the source file heat.exe dir c:\temp\Configuration\Files -ag -cg MyComp -ag -gg -g1 -ke -var Product/@Manufacturer= Product/@Manufacturer=%22ABCD - template product -out c:\temp\Configuration\wixauto\mainsource.wxs thanks! -- View this message in context: http://windows-installer-xml-wix- toolset.687559.n2.nabble.com/Heat-exe-How-to-pass-Product- Manufacturer-Name-Title-version
[WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version
Hi all, I am trying to generate a wxs source file using Heat.exe and wanted to check if I can pass values for Manufacturer, Name, Title and version to heat.exe? I tried using -var argument, but does nt seem to update it to the source file heat.exe dir c:\temp\Configuration\Files -ag -cg MyComp -ag -gg -g1 -ke -var Product/@Manufacturer= Product/@Manufacturer=%22ABCD -template product -out c:\temp\Configuration\wixauto\mainsource.wxs thanks! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-exe-How-to-pass-Product-Manufacturer-Name-Title-version-tp5816654p5816654.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version
Heat does not generate a Product/ element. Heat /? shows the following documentation for -var: -var VariableName substitute File/@Source=SourceDir with a preprocessor or a wix variable (e.g. -var var.MySource will become File/@Source=$(var.MySource)\myfile.txt and -var wix.MySource will become File/@Source=!(wix.MySource)\myfile.txt This does text transformation on the generated output wxs file. I created an empty text file called test.txt and used the following command line to harvest it using heat.exe: heat file test.txt -out test.wxs Here are the contents of test.wxs: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment DirectoryRef Id=TARGETDIR Directory Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Name=code / /DirectoryRef /Fragment Fragment DirectoryRef Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Component Id=cmp5BA64E6B74419477D4B75A1E802397FC Guid=PUT-GUID-HERE File Id=fil67D465DE6C69EA3B3CD0B7487E6132B6 KeyPath=yes Source=SourceDir\code\test.txt / /Component /DirectoryRef /Fragment /Wix Notice that File/@Source=SourceDir\code\test.txt If use -var like this: heat file test.txt -out test.wxs -var var.CodeDir Then I get this: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment DirectoryRef Id=TARGETDIR Directory Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Name=code / /DirectoryRef /Fragment Fragment DirectoryRef Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Component Id=cmp5BA64E6B74419477D4B75A1E802397FC Guid=PUT-GUID-HERE File Id=fil67D465DE6C69EA3B3CD0B7487E6132B6 KeyPath=yes Source=$(var.CodeDir)\code\test.txt / /Component /DirectoryRef /Fragment /Wix Notice that File/@Source=$(var.CodeDir)\code\test.txt just like the documentation says. In a Product/ element is *not* generated in either example. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: sangeeta1 [mailto:snmsn...@gmail.com] Sent: Wednesday, December 08, 2010 12:25 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version Hi all, I am trying to generate a wxs source file using Heat.exe and wanted to check if I can pass values for Manufacturer, Name, Title and version to heat.exe? I tried using -var argument, but does nt seem to update it to the source file heat.exe dir c:\temp\Configuration\Files -ag -cg MyComp -ag -gg -g1 -ke -var Product/@Manufacturer= Product/@Manufacturer=%22ABCD - template product -out c:\temp\Configuration\wixauto\mainsource.wxs thanks! -- View this message in context: http://windows-installer-xml-wix- toolset.687559.n2.nabble.com/Heat-exe-How-to-pass-Product- Manufacturer-Name-Title-version-tp5816654p5816654.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version
I just saw the -template product parameter specified. That causes heat to generate the Product/ element. The -var parameter still works as shown previously in this case. You could use the -t parameter to specify a XSLT transform to use to modify the generated XML. You could author the XSLT transform to set those attributes to dereference a preprocessor variable: xsl:transform version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xsl:output method=xml version=1.0 encoding=utf-8 indent=yes/ xsl:template match=@Manufacturer xsl:attribute name=Manufacturer$(var.Manufacturer)/xsl:attribute /xsl:template xsl:template match=node() | @* xsl:copy xsl:apply-templates select=@* | node()/ /xsl:copy /xsl:template /xsl:transform You can define similar templates for other attributes. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Wednesday, December 08, 2010 1:58 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version Heat does not generate a Product/ element. Heat /? shows the following documentation for -var: -var VariableName substitute File/@Source=SourceDir with a preprocessor or a wix variable (e.g. -var var.MySource will become File/@Source=$(var.MySource)\myfile.txt and -var wix.MySource will become File/@Source=!(wix.MySource)\myfile.txt This does text transformation on the generated output wxs file. I created an empty text file called test.txt and used the following command line to harvest it using heat.exe: heat file test.txt -out test.wxs Here are the contents of test.wxs: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment DirectoryRef Id=TARGETDIR Directory Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Name=code / /DirectoryRef /Fragment Fragment DirectoryRef Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Component Id=cmp5BA64E6B74419477D4B75A1E802397FC Guid=PUT-GUID-HERE File Id=fil67D465DE6C69EA3B3CD0B7487E6132B6 KeyPath=yes Source=SourceDir\code\test.txt / /Component /DirectoryRef /Fragment /Wix Notice that File/@Source=SourceDir\code\test.txt If use -var like this: heat file test.txt -out test.wxs -var var.CodeDir Then I get this: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment DirectoryRef Id=TARGETDIR Directory Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Name=code / /DirectoryRef /Fragment Fragment DirectoryRef Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Component Id=cmp5BA64E6B74419477D4B75A1E802397FC Guid=PUT-GUID-HERE File Id=fil67D465DE6C69EA3B3CD0B7487E6132B6 KeyPath=yes Source=$(var.CodeDir)\code\test.txt / /Component /DirectoryRef /Fragment /Wix Notice that File/@Source=$(var.CodeDir)\code\test.txt just like the documentation says. In a Product/ element is *not* generated in either example. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: sangeeta1 [mailto:snmsn...@gmail.com] Sent: Wednesday, December 08, 2010 12:25 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version Hi all, I am trying to generate a wxs source file using Heat.exe and wanted to check if I can pass values for Manufacturer, Name, Title and version to heat.exe? I tried using -var argument, but does nt seem to update it to the source file heat.exe dir c:\temp\Configuration\Files -ag -cg MyComp -ag -gg -g1 -ke -var Product/@Manufacturer= Product/@Manufacturer=%22ABCD - template product -out c:\temp\Configuration\wixauto\mainsource.wxs thanks! -- View this message in context: http://windows-installer-xml-wix- toolset.687559.n2.nabble.com/Heat-exe-How-to-pass-Product- Manufacturer-Name-Title-version-tp5816654p5816654.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version
Product element can be generated by giving -template Product in the argument. If you type heat , you will see its syntax. And I think -var is only used for the SourceDir and not to replace any attribute in the file. This is my understanding, but please correct me if this is not right. Looks like I will have to load the xml in XmlDocument and update the attributes I want. Thanks for your example. sangeeta On Wed, Dec 8, 2010 at 5:01 PM, Edwin G. Castro [via Windows Installer XML (WiX) toolset] ml-node+5816953-1419466290-306...@n2.nabble.comml-node%2b5816953-1419466290-306...@n2.nabble.com wrote: Heat does not generate a Product/ element. Heat /? shows the following documentation for -var: -var VariableName substitute File/@Source=SourceDir with a preprocessor or a wix variable (e.g. -var var.MySource will become File/@Source=$(var.MySource)\myfile.txt and -var wix.MySource will become File/@Source=!(wix.MySource)\myfile.txt This does text transformation on the generated output wxs file. I created an empty text file called test.txt and used the following command line to harvest it using heat.exe: heat file test.txt -out test.wxs Here are the contents of test.wxs: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment DirectoryRef Id=TARGETDIR Directory Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Name=code / /DirectoryRef /Fragment Fragment DirectoryRef Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Component Id=cmp5BA64E6B74419477D4B75A1E802397FC Guid=PUT-GUID-HERE File Id=fil67D465DE6C69EA3B3CD0B7487E6132B6 KeyPath=yes Source=SourceDir\code\test.txt / /Component /DirectoryRef /Fragment /Wix Notice that File/@Source=SourceDir\code\test.txt If use -var like this: heat file test.txt -out test.wxs -var var.CodeDir Then I get this: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment DirectoryRef Id=TARGETDIR Directory Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Name=code / /DirectoryRef /Fragment Fragment DirectoryRef Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Component Id=cmp5BA64E6B74419477D4B75A1E802397FC Guid=PUT-GUID-HERE File Id=fil67D465DE6C69EA3B3CD0B7487E6132B6 KeyPath=yes Source=$(var.CodeDir)\code\test.txt / /Component /DirectoryRef /Fragment /Wix Notice that File/@Source=$(var.CodeDir)\code\test.txt just like the documentation says. In a Product/ element is *not* generated in either example. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: sangeeta1 [mailto:[hidden email]http://user/SendEmail.jtp?type=nodenode=5816953i=0] Sent: Wednesday, December 08, 2010 12:25 PM To: [hidden email]http://user/SendEmail.jtp?type=nodenode=5816953i=1 Subject: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version Hi all, I am trying to generate a wxs source file using Heat.exe and wanted to check if I can pass values for Manufacturer, Name, Title and version to heat.exe? I tried using -var argument, but does nt seem to update it to the source file heat.exe dir c:\temp\Configuration\Files -ag -cg MyComp -ag -gg -g1 -ke -var Product/@Manufacturer= Product/@Manufacturer=%22ABCD - template product -out c:\temp\Configuration\wixauto\mainsource.wxs thanks! -- View this message in context: http://windows-installer-xml-wix- toolset.687559.n2.nabble.com/Heat-exe-How-to-pass-Product- Manufacturer-Name-Title-version-tp5816654p5816654.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com ___ WiX-users mailing list [hidden email] http://user/SendEmail.jtp?type=nodenode=5816953i=2 https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com ___ WiX-users mailing list [hidden email] http://user/SendEmail.jtp?type=nodenode=5816953i=3 https://lists.sourceforge.net/lists/listinfo/wix-users -- View message @ http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-exe-How-to-pass-Product-Manufacturer-Name-Title-version-tp5816654p5816953.html To start a new topic under wix-users, email
Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version
After trying out an example, I see the significance of the -var variable. Regarding you example in using -var How can I replace the value of Source to a physical path of the root folder (like c:\temp\test) without having to use a wix variable var.MySource? I am automating the generation of msi given a set of installable files. I will be invoking these commands from .net program. many thanks for your help on this.. On Wed, Dec 8, 2010 at 5:01 PM, Edwin G. Castro [via Windows Installer XML (WiX) toolset] ml-node+5816953-1419466290-306...@n2.nabble.comml-node%2b5816953-1419466290-306...@n2.nabble.com wrote: Heat does not generate a Product/ element. Heat /? shows the following documentation for -var: -var VariableName substitute File/@Source=SourceDir with a preprocessor or a wix variable (e.g. -var var.MySource will become File/@Source=$(var.MySource)\myfile.txt and -var wix.MySource will become File/@Source=!(wix.MySource)\myfile.txt This does text transformation on the generated output wxs file. I created an empty text file called test.txt and used the following command line to harvest it using heat.exe: heat file test.txt -out test.wxs Here are the contents of test.wxs: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment DirectoryRef Id=TARGETDIR Directory Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Name=code / /DirectoryRef /Fragment Fragment DirectoryRef Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Component Id=cmp5BA64E6B74419477D4B75A1E802397FC Guid=PUT-GUID-HERE File Id=fil67D465DE6C69EA3B3CD0B7487E6132B6 KeyPath=yes Source=SourceDir\code\test.txt / /Component /DirectoryRef /Fragment /Wix Notice that File/@Source=SourceDir\code\test.txt If use -var like this: heat file test.txt -out test.wxs -var var.CodeDir Then I get this: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment DirectoryRef Id=TARGETDIR Directory Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Name=code / /DirectoryRef /Fragment Fragment DirectoryRef Id=dir22FE4E6795D49A83D8CC3F97AEACA344 Component Id=cmp5BA64E6B74419477D4B75A1E802397FC Guid=PUT-GUID-HERE File Id=fil67D465DE6C69EA3B3CD0B7487E6132B6 KeyPath=yes Source=$(var.CodeDir)\code\test.txt / /Component /DirectoryRef /Fragment /Wix Notice that File/@Source=$(var.CodeDir)\code\test.txt just like the documentation says. In a Product/ element is *not* generated in either example. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: sangeeta1 [mailto:[hidden email]http://user/SendEmail.jtp?type=nodenode=5816953i=0] Sent: Wednesday, December 08, 2010 12:25 PM To: [hidden email]http://user/SendEmail.jtp?type=nodenode=5816953i=1 Subject: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name, Title, version Hi all, I am trying to generate a wxs source file using Heat.exe and wanted to check if I can pass values for Manufacturer, Name, Title and version to heat.exe? I tried using -var argument, but does nt seem to update it to the source file heat.exe dir c:\temp\Configuration\Files -ag -cg MyComp -ag -gg -g1 -ke -var Product/@Manufacturer= Product/@Manufacturer=%22ABCD - template product -out c:\temp\Configuration\wixauto\mainsource.wxs thanks! -- View this message in context: http://windows-installer-xml-wix- toolset.687559.n2.nabble.com/Heat-exe-How-to-pass-Product- Manufacturer-Name-Title-version-tp5816654p5816654.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com ___ WiX-users mailing list [hidden email] http://user/SendEmail.jtp?type=nodenode=5816953i=2 https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com ___ WiX-users mailing list [hidden email] http://user/SendEmail.jtp?type=nodenode=5816953i=3 https://lists.sourceforge.net/lists/listinfo/wix-users -- View message @ http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-exe-How-to-pass-Product-Manufacturer-Name-Title-version-tp5816654p5816953.html To start a new topic under wix
Re: [WiX-users] heat.exe runtime error (r6034)
Brian, Thank you for the detailed explanation. I will definitely consider this issue. I know that the company is ISV for Miscrosoft, however, if there is only one doubt about rights to create a single package that includes both the application and SQL server express, my suggestion to them will be to keep those separeted. I will surely consider this issue. This will be just a matter for the final costomer... I'm just a contractor. Thank you. L -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-exe-runtime-error-r6034-tp5554376p5646742.html Sent from the wix-users mailing list archive at Nabble.com. -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe runtime error (r6034)
You may be just a contractor but (while I am not a lawyer nor do I play one on TV) that may not absolve you of your liability for your role in license violations if repackaging is not allowed by your client's license to the repackaged product. I would seek indemnity from your client if they insist on going forward that way. I'd also recommend informing them that they are taking on the burden of becoming responsible for any security issues that exist in the repackaged application, even if they don't have source code or any means of repairing the security issues. The same goes for any and all repackaged applications. In general, you never want to repackage unless the vendor's/provider's license or distribution instructions explicitly allows it. This applies to both FOSS and proprietary licensed software. -Original Message- From: zero51 [mailto:luca.taro...@faacgroup.com] Sent: Monday, October 18, 2010 4:55 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] heat.exe runtime error (r6034) Brian, Thank you for the detailed explanation. I will definitely consider this issue. I know that the company is ISV for Miscrosoft, however, if there is only one doubt about rights to create a single package that includes both the application and SQL server express, my suggestion to them will be to keep those separeted. I will surely consider this issue. This will be just a matter for the final costomer... I'm just a contractor. Thank you. L -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-exe-runti me-error-r6034-tp5554376p5646742.html Sent from the wix-users mailing list archive at Nabble.com. -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe runtime error (r6034)
Hey Luca, Distribution and repackaging are two different matters. I highly doubt you have the rights to repackage SQL Server. If you consume their MSI's and/or merge modules as-is I am sure this would be fine. However, when you change their deployment packages you have effectively created a different product. Besides the basics where the Product Code and GUIDs in the MSIs/Merge Modules would be changed and now unserviceable by Microsoft, you are taking on owership of someone else's product in a manner they don't control. Please claify your intents and what you are trying to accomplish. Thanks, Brian Rogers Intelligence removes complexity. - Me http://blogs.msdn.com/icumove On Wed, Oct 13, 2010 at 12:03 AM, zero51 luca.taro...@faacgroup.com wrote: yes, it is. The company where I work is allowed to distribute SQL server. However, I figured out the issue: the problem wes due to some switches on heat command. If I need to include in my .msi file all the installation package I need to use -sreg in order to avoid that heat looks for registry key for all the .dll of the installation. this works for me: heat dir \\bosrv01\SQLEXPR -cg SQLEXPR -sreg -gg -out D:\SQLEXPR.wxs Luca -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-exe-runtime-error-r6034-tp5554376p5629788.html Sent from the wix-users mailing list archive at Nabble.com. -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe runtime error (r6034)
yes, it is. The company where I work is allowed to distribute SQL server. However, I figured out the issue: the problem wes due to some switches on heat command. If I need to include in my .msi file all the installation package I need to use -sreg in order to avoid that heat looks for registry key for all the .dll of the installation. this works for me: heat dir \\bosrv01\SQLEXPR -cg SQLEXPR -sreg -gg -out D:\SQLEXPR.wxs Luca -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-exe-runtime-error-r6034-tp5554376p5629788.html Sent from the wix-users mailing list archive at Nabble.com. -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe runtime error (r6034)
Hi, I got the same problem. I am trying to harves by using heat a whole installation of SQL Server 2008. the error is the same: R6034 An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information. ... and after heat exits. My WiX version is 3.6.0905.0. This is my command line: heat dir \\bosrv01\SQLEXPR -cg SQLEXPR -gg -out D:\SQLEXPR.wxs Thanks, Luca -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-exe-runtime-error-r6034-tp5554376p5625700.html Sent from the wix-users mailing list archive at Nabble.com. -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe runtime error (r6034)
I suspect the errors come from the DLL heat is loading trying to harvest. That error is a SxS/fusion failure, usually caused by incorrect/missing manifests (possibly including embedded manifests in the DLL). On a different note, is repackaging SQL Server (any edition) legal/supported? -Original Message- From: Mark Simonetti [mailto:ma...@opalsoftware.co.uk] Sent: Tuesday, October 12, 2010 1:57 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] heat.exe runtime error (r6034) Still get the same problem here too. Not sure that there's a solution at the minute. Anyone got any ideas on this? Thanks, Mark. On 12/10/2010 08:20, zero51 wrote: Hi, I got the same problem. I am trying to harves by using heat a whole installation of SQL Server 2008. the error is the same: R6034 An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information. ... and after heat exits. My WiX version is 3.6.0905.0. This is my command line: heat dir \\bosrv01\SQLEXPR -cg SQLEXPR -gg -out D:\SQLEXPR.wxs Thanks, Luca -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId
Yes, heat and tallow ran on win7 x64.
Are there any written rules one must follow when trying to gather
registry information? Must the machine be 32-bit, etc...? These are
32-bit c++ dlls.
Thanks,
Jon
On Tue, Oct 5, 2010 at 10:10 PM, Blair os...@live.com wrote:
You don't say if the XP is 32 or 64 bit. You also didn't mention trying it
on 32-bit Win7.
I think it is a bitness issue, and the binary you are harvesting may be
written to accommodate it. According to this page
[http://msdn.microsoft.com/en-us/library/ms680091(v=VS.85).aspx] what the
ProxyStubClassId attribute maps into:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{IID}
ProxyStubClsid
is used for 16-bit code, and there is no 16-bit code on 64-bit systems.
-Original Message-
When I use heat.exe v3, or tallow.exe to gather registry information
on XP, I get the following data:
Interface Id={Y2D0778B-AC99-4C58-A5C8-E7724E5316B5} Name=Hello
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046} /
When I use heat.exe v3, or tallow.exe to gather registry information
on Win7 x64, I get the following data:
Interface Id={Y2D0778B-AC99-4C58-A5C8-E7724E5316B5} Name=Hello
ProxyStubClassId32={00020424---C000-0046} /
Is there a reason for the missing ProxyStubClassId entry on Win7 x64?
Thank you,
Jon
--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId
It is recommended that COM dlls be harvested on a machine that approximates
the target machine as close as possible. Realize that due to the nature of
harvesting that there could always be discrepancies and that the only way to
know you have it right is to have the developer who makes the object write
the authoring for it explicitly (write the WiX registration code
themselves), since they are the one who (in an ideal world) best knows the
registration required for the object to operate. When running arbitrary code
(which is what heat does) that code could be reacting to just about anything
in determining what it must (or conversely does not need to) write to the
registry (or anywhere else, for that matter), which is one part of what
makes self registration non-repeatable and unstable. By using heat to
harvest registry data, you simply move the self-registration step up from
the actual installation to the build[/prep] stage. You don't eliminate the
risks caused by it, but you do control for them better (by isolating the
most frequent failures related to self-registration).
-Original Message-
From: Jon W [mailto:know...@gmail.com]
Sent: Wednesday, October 06, 2010 6:08 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId
Yes, heat and tallow ran on win7 x64.
Are there any written rules one must follow when trying to gather
registry information? Must the machine be 32-bit, etc...? These are
32-bit c++ dlls.
Thanks,
Jon
On Tue, Oct 5, 2010 at 10:10 PM, Blair os...@live.com wrote:
You don't say if the XP is 32 or 64 bit. You also didn't mention trying it
on 32-bit Win7.
I think it is a bitness issue, and the binary you are harvesting may be
written to accommodate it. According to this page
[http://msdn.microsoft.com/en-us/library/ms680091(v=VS.85).aspx] what the
ProxyStubClassId attribute maps into:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{IID}
ProxyStubClsid
is used for 16-bit code, and there is no 16-bit code on 64-bit systems.
-Original Message-
When I use heat.exe v3, or tallow.exe to gather registry information
on XP, I get the following data:
Interface Id={Y2D0778B-AC99-4C58-A5C8-E7724E5316B5} Name=Hello
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046} /
When I use heat.exe v3, or tallow.exe to gather registry information
on Win7 x64, I get the following data:
Interface Id={Y2D0778B-AC99-4C58-A5C8-E7724E5316B5} Name=Hello
ProxyStubClassId32={00020424---C000-0046} /
Is there a reason for the missing ProxyStubClassId entry on Win7 x64?
Thank you,
Jon
--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId
I know you prefaced your opion with ideal but I'll just say where I work
finding a developer who will admit knowing anything about COM is getting really
difficult. So what I do is approximate the COM as good as I can and go deploy
the package. If anyone reports a problem I grab a program call InstallWatch
and
snapshot/diff the registry after manually invoking RegSvr32 / Regasm and
then massage that back into my WXS source. I probably have to do that about
3-6 times per year and it usually ends up working in the end. The most common
problem I encounter missing Implemented Catagories from .NET ComVisible classes.
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
- Original Message
From: Blair os...@live.com
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Sent: Wed, October 6, 2010 1:53:41 PM
Subject: Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId
It is recommended that COM dlls be harvested on a machine that approximates
the target machine as close as possible. Realize that due to the nature of
harvesting that there could always be discrepancies and that the only way to
know you have it right is to have the developer who makes the object write
the authoring for it explicitly (write the WiX registration code
themselves), since they are the one who (in an ideal world) best knows the
registration required for the object to operate. When running arbitrary code
(which is what heat does) that code could be reacting to just about anything
in determining what it must (or conversely does not need to) write to the
registry (or anywhere else, for that matter), which is one part of what
makes self registration non-repeatable and unstable. By using heat to
harvest registry data, you simply move the self-registration step up from
the actual installation to the build[/prep] stage. You don't eliminate the
risks caused by it, but you do control for them better (by isolating the
most frequent failures related to self-registration).
-Original Message-
From: Jon W [mailto:know...@gmail.com]
Sent: Wednesday, October 06, 2010 6:08 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId
Yes, heat and tallow ran on win7 x64.
Are there any written rules one must follow when trying to gather
registry information? Must the machine be 32-bit, etc...? These are
32-bit c++ dlls.
Thanks,
Jon
On Tue, Oct 5, 2010 at 10:10 PM, Blair os...@live.com wrote:
You don't say if the XP is 32 or 64 bit. You also didn't mention trying it
on 32-bit Win7.
I think it is a bitness issue, and the binary you are harvesting may be
written to accommodate it. According to this page
[http://msdn.microsoft.com/en-us/library/ms680091(v=VS.85).aspx] what the
ProxyStubClassId attribute maps into:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{IID}
ProxyStubClsid
is used for 16-bit code, and there is no 16-bit code on 64-bit systems.
-Original Message-
When I use heat.exe v3, or tallow.exe to gather registry information
on XP, I get the following data:
Interface Id={Y2D0778B-AC99-4C58-A5C8-E7724E5316B5} Name=Hello
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046} /
When I use heat.exe v3, or tallow.exe to gather registry information
on Win7 x64, I get the following data:
Interface Id={Y2D0778B-AC99-4C58-A5C8-E7724E5316B5} Name=Hello
ProxyStubClassId32={00020424---C000-0046} /
Is there a reason for the missing ProxyStubClassId entry on Win7 x64?
Thank you,
Jon
--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Beautiful is writing same markup. Internet Explorer 9 supports
standards
Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId
The aggregate quality of the practitioners of our craft does seem to be
sliding downhill, doesn't it? I've even read that they have even been
dumbing down the educational achievement necessary to get a CompSci degree
this past decade. People in general seem to just want to get their work
done and don't want to be bothered with actually learning about how what
they work on actually works (what I call programming the black box).
I've never been a black-box kind-of guy. I have a huge need to know what I'm
doing whenever I embark on a project. While I obviously can't know-it-all,
I do dive deep (as much as possible) into what I do work with on any kind of
ongoing basis so that I can understand both the limitations and the
possibilities of what can be done. I guess I'm a rare breed these days,
though.
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: Wednesday, October 06, 2010 12:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId
I know you prefaced your opion with ideal but I'll just say where I work
finding a developer who will admit knowing anything about COM is getting
really
difficult. So what I do is approximate the COM as good as I can and go
deploy
the package. If anyone reports a problem I grab a program call InstallWatch
and
snapshot/diff the registry after manually invoking RegSvr32 / Regasm and
then massage that back into my WXS source. I probably have to do that
about
3-6 times per year and it usually ends up working in the end. The most
common
problem I encounter missing Implemented Catagories from .NET ComVisible
classes.
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
- Original Message
From: Blair os...@live.com
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Sent: Wed, October 6, 2010 1:53:41 PM
Subject: Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId
It is recommended that COM dlls be harvested on a machine that approximates
the target machine as close as possible. Realize that due to the nature of
harvesting that there could always be discrepancies and that the only way to
know you have it right is to have the developer who makes the object write
the authoring for it explicitly (write the WiX registration code
themselves), since they are the one who (in an ideal world) best knows the
registration required for the object to operate. When running arbitrary code
(which is what heat does) that code could be reacting to just about anything
in determining what it must (or conversely does not need to) write to the
registry (or anywhere else, for that matter), which is one part of what
makes self registration non-repeatable and unstable. By using heat to
harvest registry data, you simply move the self-registration step up from
the actual installation to the build[/prep] stage. You don't eliminate the
risks caused by it, but you do control for them better (by isolating the
most frequent failures related to self-registration).
-Original Message-
From: Jon W [mailto:know...@gmail.com]
Sent: Wednesday, October 06, 2010 6:08 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId
Yes, heat and tallow ran on win7 x64.
Are there any written rules one must follow when trying to gather
registry information? Must the machine be 32-bit, etc...? These are
32-bit c++ dlls.
Thanks,
Jon
On Tue, Oct 5, 2010 at 10:10 PM, Blair os...@live.com wrote:
You don't say if the XP is 32 or 64 bit. You also didn't mention trying it
on 32-bit Win7.
I think it is a bitness issue, and the binary you are harvesting may be
written to accommodate it. According to this page
[http://msdn.microsoft.com/en-us/library/ms680091(v=VS.85).aspx] what the
ProxyStubClassId attribute maps into:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{IID}
ProxyStubClsid
is used for 16-bit code, and there is no 16-bit code on 64-bit systems.
-Original Message-
When I use heat.exe v3, or tallow.exe to gather registry information
on XP, I get the following data:
Interface Id={Y2D0778B-AC99-4C58-A5C8-E7724E5316B5} Name=Hello
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046} /
When I use heat.exe v3, or tallow.exe to gather registry information
on Win7 x64, I get the following data:
Interface Id={Y2D0778B-AC99-4C58-A5C8-E7724E5316B5} Name=Hello
ProxyStubClassId32={00020424---C000-0046} /
Is there a reason for the missing ProxyStubClassId entry on Win7 x64?
Thank you,
Jon
--
Beautiful is writing same markup. Internet Explorer 9 supports
Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId
So, the answer is good luck using harvesting tools as they may not
always work. Not really a confidence booster, but they seem to work
for the most part.
Thanks,
Jon
On Wed, Oct 6, 2010 at 1:38 PM, Blair os...@live.com wrote:
The aggregate quality of the practitioners of our craft does seem to be
sliding downhill, doesn't it? I've even read that they have even been
dumbing down the educational achievement necessary to get a CompSci degree
this past decade. People in general seem to just want to get their work
done and don't want to be bothered with actually learning about how what
they work on actually works (what I call programming the black box).
I've never been a black-box kind-of guy. I have a huge need to know what I'm
doing whenever I embark on a project. While I obviously can't know-it-all,
I do dive deep (as much as possible) into what I do work with on any kind of
ongoing basis so that I can understand both the limitations and the
possibilities of what can be done. I guess I'm a rare breed these days,
though.
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: Wednesday, October 06, 2010 12:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId
I know you prefaced your opion with ideal but I'll just say where I work
finding a developer who will admit knowing anything about COM is getting
really
difficult. So what I do is approximate the COM as good as I can and go
deploy
the package. If anyone reports a problem I grab a program call InstallWatch
and
snapshot/diff the registry after manually invoking RegSvr32 / Regasm and
then massage that back into my WXS source. I probably have to do that
about
3-6 times per year and it usually ends up working in the end. The most
common
problem I encounter missing Implemented Catagories from .NET ComVisible
classes.
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
- Original Message
From: Blair os...@live.com
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Sent: Wed, October 6, 2010 1:53:41 PM
Subject: Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId
It is recommended that COM dlls be harvested on a machine that approximates
the target machine as close as possible. Realize that due to the nature of
harvesting that there could always be discrepancies and that the only way to
know you have it right is to have the developer who makes the object write
the authoring for it explicitly (write the WiX registration code
themselves), since they are the one who (in an ideal world) best knows the
registration required for the object to operate. When running arbitrary code
(which is what heat does) that code could be reacting to just about anything
in determining what it must (or conversely does not need to) write to the
registry (or anywhere else, for that matter), which is one part of what
makes self registration non-repeatable and unstable. By using heat to
harvest registry data, you simply move the self-registration step up from
the actual installation to the build[/prep] stage. You don't eliminate the
risks caused by it, but you do control for them better (by isolating the
most frequent failures related to self-registration).
-Original Message-
From: Jon W [mailto:know...@gmail.com]
Sent: Wednesday, October 06, 2010 6:08 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId
Yes, heat and tallow ran on win7 x64.
Are there any written rules one must follow when trying to gather
registry information? Must the machine be 32-bit, etc...? These are
32-bit c++ dlls.
Thanks,
Jon
On Tue, Oct 5, 2010 at 10:10 PM, Blair os...@live.com wrote:
You don't say if the XP is 32 or 64 bit. You also didn't mention trying it
on 32-bit Win7.
I think it is a bitness issue, and the binary you are harvesting may be
written to accommodate it. According to this page
[http://msdn.microsoft.com/en-us/library/ms680091(v=VS.85).aspx] what the
ProxyStubClassId attribute maps into:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{IID}
ProxyStubClsid
is used for 16-bit code, and there is no 16-bit code on 64-bit systems.
-Original Message-
When I use heat.exe v3, or tallow.exe to gather registry information
on XP, I get the following data:
Interface Id={Y2D0778B-AC99-4C58-A5C8-E7724E5316B5} Name=Hello
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046} /
When I use heat.exe v3, or tallow.exe to gather registry information
on Win7 x64, I get the following data:
Interface Id={Y2D0778B-AC99-4C58-A5C8-E7724E5316B5} Name=Hello
Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId
Pretty much; COM extracting is a black art. Sometimes it works and sometimes it doesn't. I'll admit it, I'm not a COM god. But I keep a variety of tools at my side ( InstallShield COM extract, Heat Harvesting, OleView, InstallWatch ) and make good use of version control, build automation and lab virtualization along with some good old fashioned sluething until I get it working correctly. Then I leave it the hell alone. Oh, and keep muttering COM sucks to developers to encourage them to use more managed code. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Jon W know...@gmail.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, October 6, 2010 5:12:51 PM Subject: Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId So, the answer is good luck using harvesting tools as they may not always work. Not really a confidence booster, but they seem to work for the most part. Thanks, Jon On Wed, Oct 6, 2010 at 1:38 PM, Blair os...@live.com wrote: The aggregate quality of the practitioners of our craft does seem to be sliding downhill, doesn't it? I've even read that they have even been dumbing down the educational achievement necessary to get a CompSci degree this past decade. People in general seem to just want to get their work done and don't want to be bothered with actually learning about how what they work on actually works (what I call programming the black box). I've never been a black-box kind-of guy. I have a huge need to know what I'm doing whenever I embark on a project. While I obviously can't know-it-all, I do dive deep (as much as possible) into what I do work with on any kind of ongoing basis so that I can understand both the limitations and the possibilities of what can be done. I guess I'm a rare breed these days, though. -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Wednesday, October 06, 2010 12:14 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId I know you prefaced your opion with ideal but I'll just say where I work finding a developer who will admit knowing anything about COM is getting really difficult. So what I do is approximate the COM as good as I can and go deploy the package. If anyone reports a problem I grab a program call InstallWatch and snapshot/diff the registry after manually invoking RegSvr32 / Regasm and then massage that back into my WXS source. I probably have to do that about 3-6 times per year and it usually ends up working in the end. The most common problem I encounter missing Implemented Catagories from .NET ComVisible classes. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Blair os...@live.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, October 6, 2010 1:53:41 PM Subject: Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId It is recommended that COM dlls be harvested on a machine that approximates the target machine as close as possible. Realize that due to the nature of harvesting that there could always be discrepancies and that the only way to know you have it right is to have the developer who makes the object write the authoring for it explicitly (write the WiX registration code themselves), since they are the one who (in an ideal world) best knows the registration required for the object to operate. When running arbitrary code (which is what heat does) that code could be reacting to just about anything in determining what it must (or conversely does not need to) write to the registry (or anywhere else, for that matter), which is one part of what makes self registration non-repeatable and unstable. By using heat to harvest registry data, you simply move the self-registration step up from the actual installation to the build[/prep] stage. You don't eliminate the risks caused by it, but you do control for them better (by isolating the most frequent failures related to self-registration). -Original Message- From: Jon W [mailto:know...@gmail.com] Sent: Wednesday, October 06, 2010 6:08 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId Yes, heat and tallow ran on win7 x64. Are there any written rules one must follow when trying to gather registry information? Must the machine be 32-bit, etc...? These are 32-bit c++ dlls. Thanks, Jon On Tue, Oct 5, 2010 at 10:10 PM, Blair os...@live.com wrote: You don't say if the XP is 32 or 64 bit
[WiX-users] heat.exe registry harvesting: ProxyStubClassId
When I use heat.exe v3, or tallow.exe to gather registry information
on XP, I get the following data:
Interface Id={Y2D0778B-AC99-4C58-A5C8-E7724E5316B5} Name=Hello
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046} /
When I use heat.exe v3, or tallow.exe to gather registry information
on Win7 x64, I get the following data:
Interface Id={Y2D0778B-AC99-4C58-A5C8-E7724E5316B5} Name=Hello
ProxyStubClassId32={00020424---C000-0046} /
Is there a reason for the missing ProxyStubClassId entry on Win7 x64?
Thank you,
Jon
--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId
You don't say if the XP is 32 or 64 bit. You also didn't mention trying it
on 32-bit Win7.
I think it is a bitness issue, and the binary you are harvesting may be
written to accommodate it. According to this page
[http://msdn.microsoft.com/en-us/library/ms680091(v=VS.85).aspx] what the
ProxyStubClassId attribute maps into:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{IID}
ProxyStubClsid
is used for 16-bit code, and there is no 16-bit code on 64-bit systems.
-Original Message-
From: Jon W [mailto:know...@gmail.com]
Sent: Tuesday, October 05, 2010 1:56 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] heat.exe registry harvesting: ProxyStubClassId
When I use heat.exe v3, or tallow.exe to gather registry information
on XP, I get the following data:
Interface Id={Y2D0778B-AC99-4C58-A5C8-E7724E5316B5} Name=Hello
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046} /
When I use heat.exe v3, or tallow.exe to gather registry information
on Win7 x64, I get the following data:
Interface Id={Y2D0778B-AC99-4C58-A5C8-E7724E5316B5} Name=Hello
ProxyStubClassId32={00020424---C000-0046} /
Is there a reason for the missing ProxyStubClassId entry on Win7 x64?
Thank you,
Jon
--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe
Thankyou Bob, This now works fine! Is it possible to set the variable within the main.wxs file so that candle picks up the value though? Sorry if this is a stupid question! -Original Message- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: 23 September 2010 01:32 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Heat.exe On 22-Sep-10 18:11, David Amey wrote: Basically I'm using heat to harvest a folder, simples. However I'm using the -var property in the command line (to replace the sourceDir in the output component's source attribute), using a variable declared in the main.wxs. This replaces the sourceDir as expected, but when it comes to candle to compile , it flags an error as if the variable isn't populated. You have to define the values for any preprocessor variables you use in your source code. How you do that depends on how you run the compiler (e.g., -d on the command line or DefineConstants in MSBuild) but both are documented in WiX.chm. -- sig://boB http://joyofsetup.com/ -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Heat.exe
Hi everyone! I've been struggling with this problem for a while, if anyone can help I would really appreciate it. Basically I'm using heat to harvest a folder, simples. However I'm using the -var property in the command line (to replace the sourceDir in the output component's source attribute), using a variable declared in the main.wxs. This replaces the sourceDir as expected, but when it comes to candle to compile , it flags an error as if the variable isn't populated. Sorry if this was hard to follow or understand (incredibly frustrated!), but if you think you can help I will try and explain a bit better. Thanks in advance! David Amey Technical Developer -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe
On 22-Sep-10 18:11, David Amey wrote: Basically I'm using heat to harvest a folder, simples. However I'm using the -var property in the command line (to replace the sourceDir in the output component's source attribute), using a variable declared in the main.wxs. This replaces the sourceDir as expected, but when it comes to candle to compile , it flags an error as if the variable isn't populated. You have to define the values for any preprocessor variables you use in your source code. How you do that depends on how you run the compiler (e.g., -d on the command line or DefineConstants in MSBuild) but both are documented in WiX.chm. -- sig://boB http://joyofsetup.com/ -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] heat.exe runtime error (r6034)
Hi all, I'm trying to harvest some files (postgres 9.0 for windows to be specific) using heat.exe. At the moment I'm keeping the command line very simple: heat dir pgsql -o test.wxs While heat is processing, I often get the following pop up: Microsoft Visual C++ Runtime Library Program: C:\Program Files\Windows Installer XML v3\bin\heat.exe R6034 An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information. Now the strange thing is I went through this process about a year ago with postgres 8.3, but I think using a slightly earlier version of the WiX toolset, and I do not remember getting this problem. Does anyone have any ideas about what might be causing this? Thanks, Mark. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe does not export COM information for a .NET component dll
That is the correct solution. Heat.exe exports COM from .NET assemblies without issue for anything I've given it including DLL/TLB pairs. Palbinder Sandher Software Deployment IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Sohail Somani [mailto:soh...@taggedtype.net] Sent: 31 August 2010 22:46 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] heat.exe does not export COM information for a .NET component dll On 10-08-31 3:25 PM, Lian Jiang wrote: Hi, I am using WIX 3.0 to export the COM registry setting from a managed component dll but I only get a file without the COM information. I can use regasm to registery this dll. I use the same heat.exe to export another .net component dll successfully. The only difference of these two dlls are the first one (where heat fails) depends on an interop assembly exported from a tlb file, while the latter (where heat succeeds) does not. Can anybody tell why heat cannot export COM information for the first one? I had this problem when heat could not load the DLL due to missing dependencies. If your component depends on something in another directory, you should add it to the path. Not sure if that is the correct solution, but it was the one I found anyway. -- Sohail Somani -- iBlog : http://uint32t.blogspot.com iTweet: http://twitter.com/somanisoftware iCode : http://bitbucket.org/cheez -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] heat.exe does not export COM information for a .NET component dll
Hi, I am using WIX 3.0 to export the COM registry setting from a managed component dll but I only get a file without the COM information. I can use regasm to registery this dll. I use the same heat.exe to export another .net component dll successfully. The only difference of these two dlls are the first one (where heat fails) depends on an interop assembly exported from a tlb file, while the latter (where heat succeeds) does not. Can anybody tell why heat cannot export COM information for the first one? Thanks Leon -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe does not export COM information for a .NET component dll
On 10-08-31 3:25 PM, Lian Jiang wrote: Hi, I am using WIX 3.0 to export the COM registry setting from a managed component dll but I only get a file without the COM information. I can use regasm to registery this dll. I use the same heat.exe to export another .net component dll successfully. The only difference of these two dlls are the first one (where heat fails) depends on an interop assembly exported from a tlb file, while the latter (where heat succeeds) does not. Can anybody tell why heat cannot export COM information for the first one? I had this problem when heat could not load the DLL due to missing dependencies. If your component depends on something in another directory, you should add it to the path. Not sure if that is the correct solution, but it was the one I found anyway. -- Sohail Somani -- iBlog : http://uint32t.blogspot.com iTweet: http://twitter.com/somanisoftware iCode : http://bitbucket.org/cheez -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe: Harvest contents of directory and NOT the directory name
Thanks for the reply, However, I do not see suppress root directory flag viewing the following heat.exe documentation link: http://wix.sourceforge.net/manual-wix3/heat.htm http://wix.sourceforge.net/manual-wix3/heat.htm - Thanks Jeff in Seattle -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-exe-Harvest-contents-of-directory-and-NOT-the-directory-name-tp4977248p4978558.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe: Harvest contents of directory and NOT the directory name
I took some hunting but I found the flag (have not tried it yet) http://www.tramontana.co.hu/wix/lesson6.php http://www.tramontana.co.hu/wix/lesson6.php Yet another switch, -srd will suppress the identifier generation for the root folder specified. File components in the root folder will refer to their Directory as either TARGETDIR or the name specified in the -dr switch and there will be no separate DirectoryRef fragment for the root folder: heat dir path -srd -dr MyDirName -cg SampleGroup -out SampleGroup.wxs - Thanks Jeff in Seattle -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-exe-Harvest-contents-of-directory-and-NOT-the-directory-name-tp4977248p4978597.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe: Harvest contents of directory and NOT the directory name
heat.exe /? goes a long way Palbinder Sandher Software Deployment IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: jeff00seattle [mailto:jeff_tan...@earthlink.net] Sent: 29 April 2010 07:33 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] heat.exe: Harvest contents of directory and NOT the directory name Thanks for the reply, However, I do not see suppress root directory flag viewing the following heat.exe documentation link: http://wix.sourceforge.net/manual-wix3/heat.htm http://wix.sourceforge.net/manual-wix3/heat.htm - Thanks Jeff in Seattle -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-exe-H arvest-contents-of-directory-and-NOT-the-directory-name-tp4977248p497855 8.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] heat.exe: Harvest contents of directory and NOT the directory name
Hi I have a directory .\foo\ that has contents I want to harvest. However, in the end, my INSTALLDIR within Harvester.wxs contains directory foo and then its components, and I want only want is components. In other words, my current harvest is this... Fragment DirectoryRef Id=INSTALLDIR Directory Id=dir###... Name=foo Component Id=cmp###... Guid=GUID File Id=fil###... KeyPath=yes Source=$(var.SourceDir)\README.txt / /Component But I want my harvest instead to be without Directory Id=dir###... Name=foo: Fragment DirectoryRef Id=INSTALLDIR Component Id=cmp###... Guid=GUID File Id=fil###... KeyPath=yes Source=$(var.SourceDir)\README.txt / /Component This is my harvest setup: heat.exe dir foo -gg -g1 -cg $(var.ComponentGroupName) -dr INSTALLDIR -nologo -sfrag -ke -out Harvester.wxs -var var.SourceDir candle.exe -nologo Harvester.wxs -out Harvester.wixobj -dSourceDir=foo -dComponentGroupName=foo_group -arch x86 light.exe -nologo Harvester.wixobj -out foo.msi -pdbout foo.wixpdb - Thanks Jeff in Seattle -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-exe-Harvest-contents-of-directory-and-NOT-the-directory-name-tp4977248p4977248.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe: Harvest contents of directory and NOT the directory name
There's a suppress root directory flag on heat.exe that controls this for you. Thanks, Navid -Original Message- From: jeff00seattle [mailto:jeff_tan...@earthlink.net] Sent: Wednesday, April 28, 2010 3:14 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] heat.exe: Harvest contents of directory and NOT the directory name Hi I have a directory .\foo\ that has contents I want to harvest. However, in the end, my INSTALLDIR within Harvester.wxs contains directory foo and then its components, and I want only want is components. In other words, my current harvest is this... Fragment DirectoryRef Id=INSTALLDIR Directory Id=dir###... Name=foo Component Id=cmp###... Guid=GUID File Id=fil###... KeyPath=yes Source=$(var.SourceDir)\README.txt / /Component But I want my harvest instead to be without Directory Id=dir###... Name=foo: Fragment DirectoryRef Id=INSTALLDIR Component Id=cmp###... Guid=GUID File Id=fil###... KeyPath=yes Source=$(var.SourceDir)\README.txt / /Component This is my harvest setup: heat.exe dir foo -gg -g1 -cg $(var.ComponentGroupName) -dr INSTALLDIR -nologo -sfrag -ke -out Harvester.wxs -var var.SourceDir candle.exe -nologo Harvester.wxs -out Harvester.wixobj -dSourceDir=foo -dComponentGroupName=foo_group -arch x86 light.exe -nologo Harvester.wixobj -out foo.msi -pdbout foo.wixpdb - Thanks Jeff in Seattle -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-exe-Harvest-contents-of-directory-and-NOT-the-directory-name-tp4977248p4977248.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe: Add attribute Win64=yes to Component elements?
Oohhh... nifty! Thanks for pointing that out Bob :) On Sun, Apr 25, 2010 at 11:42 PM, Bob Arnson b...@joyofsetup.com wrote: On 4/22/2010 7:29 PM, Sascha Beaumont wrote: No, heat doesn't harvest 64-bit information. I just do a find/replace (sed would work from the command line if it needs scripting) Find: Guid=* Replace: Guid=* Win64=yes If you use the -arch switch, Candle will do that for you. -- sig://boB http://joyofsetup.com/ -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe: Add attribute Win64=yes to Component elements?
On 4/22/2010 7:29 PM, Sascha Beaumont wrote: No, heat doesn't harvest 64-bit information. I just do a find/replace (sed would work from the command line if it needs scripting) Find: Guid=* Replace: Guid=* Win64=yes If you use the -arch switch, Candle will do that for you. -- sig://boB http://joyofsetup.com/ -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] heat.exe: Add attribute Win64=yes to Component elements?
Hi I am using heat.exe of WiX 3.0. Can it add attribute Win64=yes to Component elements when it harvests? - Thanks Jeff in Seattle -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-exe-Add-attribute-Win64-yes-to-Component-elements-tp4947690p4947690.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe: Add attribute Win64=yes to Component elements?
No, heat doesn't harvest 64-bit information. I just do a find/replace (sed would work from the command line if it needs scripting) Find: Guid=* Replace: Guid=* Win64=yes Sascha On Fri, Apr 23, 2010 at 9:22 AM, jeff00seattle jeff_tan...@earthlink.net wrote: Hi I am using heat.exe of WiX 3.0. Can it add attribute Win64=yes to Component elements when it harvests? - Thanks Jeff in Seattle -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-exe-Add-attribute-Win64-yes-to-Component-elements-tp4947690p4947690.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] heat.exe warning: limit of 1600 components per feature: what will happen?
heat.exe : warning HEAT5155 : Although there are no limitations to the size of a ComponentGroup, Windows Installer has a limit of 1600 components per feature. Please consider reducing the size of ComponentGroup '$(var.ComponentGroupName)' from current count of '3037'. What is the impact of my install if I exceed 1600 components per feature? Will WiX only package 1600 components? In my case, I exceed 3000 components. Thanks - Thanks Jeff in Seattle -- View this message in context: http://n2.nabble.com/heat-exe-warning-limit-of-1600-components-per-feature-what-will-happen-tp4928703p4928703.html Sent from the wix-users mailing list archive at Nabble.com. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe warning: limit of 1600 components per feature: what will happen?
Thanks for the reply I compared source and MSI extraction using http://winmerge.org/ WinMerge , and it showed no difference. - Thanks Jeff in Seattle -- View this message in context: http://n2.nabble.com/heat-exe-warning-limit-of-1600-components-per-feature-what-will-happen-tp4928703p4928820.html Sent from the wix-users mailing list archive at Nabble.com. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] heat.exe popping up a dialog
hi, I'm generating wxs file for Sun Java Runtime using heat and unfortunately during this process, heat/jre popups an error dialog saying Java Plug-in 1.6.0_18 is not installed properly. This happens for two DLL files inside JRE and turns our sleek fully automated process into manual nightmare :-) Is it possible to configure heat to avoid that? (I guess to NOT load/execute DLL code) Also what are consequences of indexing DLL file as plain File entry without all it's extra DLL related metadata? thanks Jacek -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe popping up a dialog
ok, I figured out adding -sreg to heat command line does the trick. anyway, I'm still interested to learn, how the DLL is processed that it can throw a popup.. Jacek 2010/3/3 Jacek Pospychała jacek.pospych...@gmail.com hi, I'm generating wxs file for Sun Java Runtime using heat and unfortunately during this process, heat/jre popups an error dialog saying Java Plug-in 1.6.0_18 is not installed properly. This happens for two DLL files inside JRE and turns our sleek fully automated process into manual nightmare :-) Is it possible to configure heat to avoid that? (I guess to NOT load/execute DLL code) Also what are consequences of indexing DLL file as plain File entry without all it's extra DLL related metadata? thanks Jacek -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe popping up a dialog
On 3/3/2010 5:02 AM, Jacek Pospychała wrote: anyway, I'm still interested to learn, how the DLL is processed that it can throw a popup.. Self-reg runs code in the DLL; it can do anything, which is one of the reasons it's evil in an installer. -- sig://boB http://joyofsetup.com/ -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe and 64-bit compatibility
Yeah, it's not trivial but we should solve this problem eventually. On Thu, Jan 14, 2010 at 8:52 AM, Brian Rogers rogers.br...@gmail.comwrote: Not sure if it is that straight forward. I think the reason we keep punting this feature is the dependencies heat.exe has on the Wix core project ( http://sourceforge.net/tracker/index.php?func=detailaid=2012626group_id=105970atid=642717 ). Brian Rogers Intelligence removes complexity. - Me http://blogs.msdn.com/icumove -- NEW On Wed, Jan 13, 2010 at 5:32 PM, Bob Arnson b...@joyofsetup.com wrote: On 1/13/2010 8:07 PM, Navid Azimi-Garakani wrote: Is there a particular reason why Heat.exe is targeted and compiled specifically against the x86 architecture? Because an MSIL .exe runs as a 64-bit process on an x64 system, so it couldn't load x86 DLLs. I suspect there's a need for Heat64. I may try my hand at compiling the Heat project for 64-bit process architectures if that's what it comes down to. Any help before it gets ugly would be much appreciated! Should be pretty straightforward, just get an enlistment. -- sig://boB http://joyofsetup.com/ -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe and 64-bit compatibility
Not sure if it is that straight forward. I think the reason we keep punting this feature is the dependencies heat.exe has on the Wix core project ( http://sourceforge.net/tracker/index.php?func=detailaid=2012626group_id=105970atid=642717 ). Brian Rogers Intelligence removes complexity. - Me http://blogs.msdn.com/icumove -- NEW On Wed, Jan 13, 2010 at 5:32 PM, Bob Arnson b...@joyofsetup.com wrote: On 1/13/2010 8:07 PM, Navid Azimi-Garakani wrote: Is there a particular reason why Heat.exe is targeted and compiled specifically against the x86 architecture? Because an MSIL .exe runs as a 64-bit process on an x64 system, so it couldn't load x86 DLLs. I suspect there's a need for Heat64. I may try my hand at compiling the Heat project for 64-bit process architectures if that's what it comes down to. Any help before it gets ugly would be much appreciated! Should be pretty straightforward, just get an enlistment. -- sig://boB http://joyofsetup.com/ -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] heat.exe
Hi, I have some problems to migrate from WIX 3.0.4707 to WIX 3.0.5419 because the arguments of HEAT.EXE changed. usage: heat.exe harvestType harvestSource harvester arguments -o[ut] sourceFile.wxs What is meant with the new argument harvestSource? The old command looks like this: C:\Program Files\Windows Installer XML v3\bin\heat.exe dir ..\..\~tmp\j2build3v_win\apps -gg -sfrag -scom -sreg $(ProjectDir)..\..\..\~tmp\j2build3v_win\apps\eu -out $(ProjectDir)gen_fragment.wxs -template:fragment How can I convert it to the new implemtation of HEAT? Mit freundlichen Grüßen / Kind regards Renate Achter Software Configuration Management Development Environment UGF7D2 GCC Development Services Open UniCredit Global Information Services S.C.p.A. Zweigniederlassung Deutschland Am Tucherpark 12, TZ 3 OG (3.060) D-80538 München phone: +49 (89) 378-26189 fax: +49 (89) 378-33--26189 mailto:mailto:%3Cfirst renate.ach...@unicreditgroup.de --- You can find the mandatory information about UniCredit Global Information Services S.C.p.A., Zweigniederlassung Deutschland, using the following link: http://www.unicredit-global-information-services.de/pflichtangaben. Please consider the environment before printing this e-mail. Important Note: This e-mail is only intended for the person or company/organisation named as recipient. It may contain trade secrets or undisclosed and confidential information or information otherwise protected by work-product immunity or other legal regulations. If you have received this email by mistake, we kindly ask you not to copy this message or use it for any purpose nor disclose its contents to any other person. Please inform us immediately and delete the original document. In addition, please let us know if you or your company object to receiving e-mails for messages of this kind. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe
I see two directories listed below. You should only have one. C:\Program Files\Windows Installer XML v3\bin\heat.exe dir ..\..\~tmp\j2build3v_win\apps -gg -sfrag -scom -sreg $(ProjectDir)..\..\..\~tmp\j2build3v_win\apps\eu -out $(ProjectDir)gen_fragment.wxs -template:fragment Should be: C:\Program Files\Windows Installer XML v3\bin\heat.exe dir ..\..\~tmp\j2build3v_win\apps -gg -sfrag -scom -sreg -out $(ProjectDir)gen_fragment.wxs -template:fragment OR: C:\Program Files\Windows Installer XML v3\bin\heat.exe dir $(ProjectDir)..\..\..\~tmp\j2build3v_win\apps\eu -gg -sfrag -scom -sreg -out $(ProjectDir)gen_fragment.wxs -template:fragment Brian Rogers Intelligence removes complexity. - Me http://blogs.msdn.com/icumove -- NEW On Wed, Jan 13, 2010 at 8:23 AM, Achter Renate (UGIS - UniCredit Group) renate.ach...@unicreditgroup.de wrote: Hi, I have some problems to migrate from WIX 3.0.4707 to WIX 3.0.5419 because the arguments of HEAT.EXE changed. usage: heat.exe harvestType harvestSource harvester arguments -o[ut] sourceFile.wxs What is meant with the new argument harvestSource? The old command looks like this: C:\Program Files\Windows Installer XML v3\bin\heat.exe dir ..\..\~tmp\j2build3v_win\apps -gg -sfrag -scom -sreg $(ProjectDir)..\..\..\~tmp\j2build3v_win\apps\eu -out $(ProjectDir)gen_fragment.wxs -template:fragment How can I convert it to the new implemtation of HEAT? Mit freundlichen Grüßen / Kind regards Renate Achter Software Configuration Management Development Environment UGF7D2 GCC Development Services Open UniCredit Global Information Services S.C.p.A. Zweigniederlassung Deutschland Am Tucherpark 12, TZ 3 OG (3.060) D-80538 München phone: +49 (89) 378-26189 fax: +49 (89) 378-33--26189 mailto:mailto:%3Cfirst renate.ach...@unicreditgroup.de --- You can find the mandatory information about UniCredit Global Information Services S.C.p.A., Zweigniederlassung Deutschland, using the following link: http://www.unicredit-global-information-services.de/pflichtangaben. Please consider the environment before printing this e-mail. Important Note: This e-mail is only intended for the person or company/organisation named as recipient. It may contain trade secrets or undisclosed and confidential information or information otherwise protected by work-product immunity or other legal regulations. If you have received this email by mistake, we kindly ask you not to copy this message or use it for any purpose nor disclose its contents to any other person. Please inform us immediately and delete the original document. In addition, please let us know if you or your company object to receiving e-mails for messages of this kind. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Heat.exe and 64-bit compatibility
Is there a particular reason why Heat.exe is targeted and compiled specifically against the x86 architecture? I have seen a couple of questions about this around on the Internet but no firm answer or resolution. I briefly looked over the Heat code (v3.0.5419.0) and there does not seem to be anything specific that jumps out as being 64-bit incompatible. Then again, it was more a cursory glance than a walkthrough. I am currently migrating our build and development environments to 64-bit. In this process, I'd also like to migrate our current setup projects to MSBuild using the WiX targets and the HeatProject task. I may try my hand at compiling the Heat project for 64-bit process architectures if that's what it comes down to. Any help before it gets ugly would be much appreciated! By the way, using a 64-bit version of MSBuild yields the expected BadImageFormatException from heat.exe. Thanks, Navid -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe and 64-bit compatibility
On 1/13/2010 8:07 PM, Navid Azimi-Garakani wrote: Is there a particular reason why Heat.exe is targeted and compiled specifically against the x86 architecture? Because an MSIL .exe runs as a 64-bit process on an x64 system, so it couldn't load x86 DLLs. I suspect there's a need for Heat64. I may try my hand at compiling the Heat project for 64-bit process architectures if that's what it comes down to. Any help before it gets ugly would be much appreciated! Should be pretty straightforward, just get an enlistment. -- sig://boB http://joyofsetup.com/ -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe : error HEAT0001 : Value cannot be null.
I don't think that the website harvester has been maintained. The guy that wrote it (a long time ago) left us (a long time ago). smile/ -Original Message- From: Joe Osman [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2008 17:38 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] heat.exe : error HEAT0001 : Value cannot be null. I am getting an exception when I try to harvest a website using Heat.exe: heat.exe : error HEAT0001 : Value cannot be null. Parameter name: child Exception Type: System.ArgumentNullException Stack Trace: at Microsoft.Tools.WindowsInstallerXml.Extensions.Serialize.IIs.WebSite.AddCh ild(ISchemaElement child) at Microsoft.Tools.WindowsInstallerXml.Extensions.IIsWebSiteHarvester.Harvest WebSite(DirectoryEntry webSiteEntry) at Microsoft.Tools.WindowsInstallerXml.Extensions.IIsWebSiteHarvester.Harvest WebSite(String name) at Microsoft.Tools.WindowsInstallerXml.Extensions.IIsWebSiteHarvester.Harvest (String argument) at Microsoft.Tools.WindowsInstallerXml.Harvester.Harvest(String argument) at Microsoft.Tools.WindowsInstallerXml.Tools.Heat.Run(String[] args) === This email, including any attachments, is only for the intended addressee. It is subject to copyright, is confidential and may be the subject of legal or other privilege, none of which is waived or lost by reason of this transmission. If the receiver is not the intended addressee, please accept our apologies, notify us by return, delete all copies and perform no other act on the email. Unfortunately, we cannot warrant that the email has not been altered or corrupted during transmission. === - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] heat.exe : error HEAT0001 : Value cannot be null.
I am getting an exception when I try to harvest a website using Heat.exe: heat.exe : error HEAT0001 : Value cannot be null. Parameter name: child Exception Type: System.ArgumentNullException Stack Trace: at Microsoft.Tools.WindowsInstallerXml.Extensions.Serialize.IIs.WebSite.AddCh ild(ISchemaElement child) at Microsoft.Tools.WindowsInstallerXml.Extensions.IIsWebSiteHarvester.Harvest WebSite(DirectoryEntry webSiteEntry) at Microsoft.Tools.WindowsInstallerXml.Extensions.IIsWebSiteHarvester.Harvest WebSite(String name) at Microsoft.Tools.WindowsInstallerXml.Extensions.IIsWebSiteHarvester.Harvest (String argument) at Microsoft.Tools.WindowsInstallerXml.Harvester.Harvest(String argument) at Microsoft.Tools.WindowsInstallerXml.Tools.Heat.Run(String[] args) === This email, including any attachments, is only for the intended addressee. It is subject to copyright, is confidential and may be the subject of legal or other privilege, none of which is waived or lost by reason of this transmission. If the receiver is not the intended addressee, please accept our apologies, notify us by return, delete all copies and perform no other act on the email. Unfortunately, we cannot warrant that the email has not been altered or corrupted during transmission. === - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe and '1 directory - 1 component' mode
Yan Sklyarenko wrote: Does heat.exe utility support the mode 1 directory - 1 component, when it harvests all the files of a certain directory to a single component? No. Harvesting one file per component helps prevent component-rule violations. -- sig://boB http://joyofsetup.com/ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Heat.exe and '1 directory - 1 component' mode
Hello WiX community, Does heat.exe utility support the mode 1 directory - 1 component, when it harvests all the files of a certain directory to a single component? I failed to find this option playing with the command-line switches, but tallow.exe could do this (-1 switch). Thank you. -- Yan - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe -scom produces incorrect regasm fragments for COM interop ?
What version of WiX are you using? The RegistryHarvester should be
handling empty leaf keys, but it may not have always been this way.
Looking at RegistrationServices (the class that both WiX and regasm.exe
use to register assemblies) Implemented Categories seems to be the
only empty key.
Jantzen, Andrej wrote:
Hello,
I tried to use heat.exe
heat.exe file -scom MyDotNetCOM.dll -out MyDotNetCOM.wxs
to generate a WiX fragment equivalent to the command
regasm MyDotNetCOM.dll /tlb
and noted that compared with execution of regasm command some things are
missing/suspect:
- the key HKCR\CLSID\{--SomeClassUUID--}\Implemented
Categories\{62C8FE65-4EBB-45E7-B440-6E39B2CDBF29}
is missing for all coclasses in my DLL (this entry marks coclasses
implemented by .NET assemblies)
- but the key
RegistryValue Root=HKCR Key=Component
Categories\{62C8FE65-4EBB-45e7-B440-6E39B2CDBF29} Name=0 Value=.NET
Category Type=string Action=write /
is created, although, in my opinion, this is a global key managed by the
.NET framework.
Is this behavour correct?
Regards,
Andrej Jantzen
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Heath Stewart
Deployment Technology Group, Microsoft
http://blogs.msdn.com/heaths
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe -scom produces incorrect regasm fragments for COM interop ?
At least 3.0.3725.0 didn't produced Implemented Categories keys.
I've now tried the version 3.0.3829.0 - it seems to do it correctly!
Thanks,
Andrej
Heath Stewart wrote:
What version of WiX are you using? The RegistryHarvester should be
handling empty leaf keys, but it may not have always been this way.
Looking at RegistrationServices (the class that both WiX and regasm.exe
use to register assemblies) Implemented Categories seems to be the
only empty key.
Jantzen, Andrej wrote:
Hello,
I tried to use heat.exe
heat.exe file -scom MyDotNetCOM.dll -out MyDotNetCOM.wxs
to generate a WiX fragment equivalent to the command
regasm MyDotNetCOM.dll /tlb
and noted that compared with execution of regasm command some things are
missing/suspect:
- the key HKCR\CLSID\{--SomeClassUUID--}\Implemented
Categories\{62C8FE65-4EBB-45E7-B440-6E39B2CDBF29}
is missing for all coclasses in my DLL (this entry marks coclasses
implemented by .NET assemblies)
- but the key
RegistryValue Root=HKCR Key=Component
Categories\{62C8FE65-4EBB-45e7-B440-6E39B2CDBF29} Name=0 Value=.NET
Category Type=string Action=write /
is created, although, in my opinion, this is a global key managed by the
.NET framework.
Is this behavour correct?
Regards,
Andrej Jantzen
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] heat.exe -scom produces incorrect regasm fragments for COM interop ?
Hello,
I tried to use heat.exe
heat.exe file -scom MyDotNetCOM.dll -out MyDotNetCOM.wxs
to generate a WiX fragment equivalent to the command
regasm MyDotNetCOM.dll /tlb
and noted that compared with execution of regasm command some things are
missing/suspect:
- the key HKCR\CLSID\{--SomeClassUUID--}\Implemented
Categories\{62C8FE65-4EBB-45E7-B440-6E39B2CDBF29}
is missing for all coclasses in my DLL (this entry marks coclasses
implemented by .NET assemblies)
- but the key
RegistryValue Root=HKCR Key=Component
Categories\{62C8FE65-4EBB-45e7-B440-6E39B2CDBF29} Name=0 Value=.NET
Category Type=string Action=write /
is created, although, in my opinion, this is a global key managed by the
.NET framework.
Is this behavour correct?
Regards,
Andrej Jantzen
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe throws up Runtime Error
Just did, same problem. I have a simplified example dll that triggers the error, however it may not be useful without the context of the software it is intended for (it's a plug-in). I'm not going to spam the list with an attachment, but I can send it directly to anyone who'd like to check it out. cheers, -Mark On 25-Feb-08, at 7:36 AM, Schrieken, Rene wrote: Can you try an earlier build (3704 for example) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Visser Sent: maandag 25 februari 2008 8:44 To: wix-users@lists.sourceforge.net Subject: [WiX-users] heat.exe throws up Runtime Error I get an error when I try to use heat.exe. Command line: heat dir mydir -out somefile.wxs Error: Runtime Error! Program c:\Program Files\Windows Installer XML v3\bin\heat.exe R6034 An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information. More info: wix 3.0.3815.0 windows XP (SP3) visual studio 2005 and 2008 installed It seems that heat.exe fails when trying to harvest information from dlls in the directory. The dlls are linked with various different other dlls and load fine in the software they are intended for (i.e. all their dependencies are in PATH, including a msvcr80.dll and Microsoft.VC80.CRT.manifest shipped with the software). Any ideas? I'd like to use heat.exe to automatically generate .wxs files, since there are hundreds of miscellaneous files in my package. thanks -Mark - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e- mail and any attachment and all copies and inform the sender. Thank you. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
