OK, thanks. A couple follow up questions:
1. The documentation says that adding Referenses "ensures that build
order dependencies are defined correctly within the solution. In
addition, it generates a set of WiX preprocessor definitions which are
set on the Candle command line and can be referenced in source files."
That all seems really neat, but I don't know how to make use of it all.
Are there any examples of how to use the preprocessor definitions?
2. Should I use *Harvest Type *of /project/ (Harvest outputs of a Visual
Studio project) for VB6 projects? Or do I want to be using the file or
dir types? The /project/ example given in the help file (and elsewhere)
is clearly for a C# project. Anyway, I can't seem to get the /project/
Harvest Type to work for any type of project; VB6; VB.NET or C#
projects. I get this output:
<output>
C:\ace-co-devel\Aceco.NET\AcecoWix>heat project -pog:Binaries -ag
-template:frag
ment -out ScXMLReader.wxs
"C:\ace-co-devel\Aceco.NET\ScXMLReader\ScXMLReader.csp
roj"
Microsoft (R) Windows Installer Xml Toolset Harvester version 3.0.5419.0
Copyright (C) Microsoft Corporation. All rights reserved.
heat.exe : error HEAT0001 : -pog:Binaries
Exception Type: System.IO.FileNotFoundException
Stack Trace:
at
Microsoft.Tools.WindowsInstallerXml.Extensions.VSProjectHarvester.Harvest(
String argument)
at Microsoft.Tools.WindowsInstallerXml.Harvester.Harvest(String
argument)
at Microsoft.Tools.WindowsInstallerXml.Tools.Heat.Run(String[] args)
</output>
The ScXMLReader.csproj exists.
3. I missed the Schema References, thanks. Are there examples that show
how to use the various extensions? Specifically the Netfx, Util,
Complus, and Sql extensions?
Thanks,
Bill McCormick
--
ACE-CO
5355 Dietrich Rd.
San Antonio, TX 78219
(210) 661-4111 x512
(800) 676-4111 Toll Free
(210) 662-6177 Fax
(210) 216-6641 Cell
mailto:[email protected]
http://www.ace-co.com
On 3/24/2010 5:48 AM, Pally Sandher wrote:
> 1 - References are probably Visual Studio's doing since you have your
> projects all in the same solution. Dark simply creates XML from an MSI,
> it doesn't create a .wixproj or modify any .sln.
>
> 2 - yes you should be using heat.exe to harvest your .NET assemblies.
>
> 3 - Surprisingly you'll find information on WiX extensions in the WiX
> documentation. See
> http://wix.sourceforge.net/manual-wix3/advanced_wix_topics_index.htm &
> http://wix.sourceforge.net/manual-wix3/schema_index.htm or your WiX.chm
> which is installed along with the WiX compilers.
>
>
> 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: Bill McCormick (LIST) [mailto:[email protected]]
> Sent: 23 March 2010 21:59
> To: WiX
> Subject: [WiX-users] .NET Applications
>
> I'm working on an installer project that has a mix of legacy VB
> applications and .NET applications.
>
> Originally, I exposed /dark /to an existing MSI, but I wasn't happy with
> the output. So I thought I'd give /heat/ a try; I used /heat /to melt
> the old VB apps down to wxs files and I can sort of see where all that's
> heading with all the various fragments and component groups.
>
> Then I noticed that my WiX project has references to all the .NET
> projects that I'd like to install and I don't recall adding the
> references. Is this something that /dark /did?
>
> Or is this a consequence of having my WiX project part of a solution
> with all the other .NET projetcts?
>
> Is this something that is required for installing .NET applications?
>
> Should I be using /heat/ to melt the bin\Release of my .NET projects? Or
> is there a better/easier method?
>
> Where can I get detailed info on all the Extensions (WixNetFxExtension,
> WixUIExtension, et. al.)?
>
>
> Thanks,
>
> Bill
>
> ------------------------------------------------------------------------
> ------
> Download Intel® 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
> ------------------------------------------------------------------------------
> Download Intel® 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
Bill McCormick
--
ACE-CO
5355 Dietrich Rd.
San Antonio, TX 78219
(210) 661-4111 x512
(800) 676-4111 Toll Free
(210) 662-6177 Fax
(210) 216-6641 Cell
mailto:[email protected]
http://www.ace-co.com
------------------------------------------------------------------------------
Download Intel® 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
