subject:"\[WiX\-users\] Building WiX"

[WiX-users] Building WIX on build machine issues...

2015-04-16 Thread Steve-Ogilvie

Hi folks,

I have a Build VM where I have installed VS2012 but have NOT installed WIX
3.9

I have rebuilt WIX 3.9 with some changes to the bootstrapper (I added some
pre requisite checks that our product requires) (If I install WIX 3.9 and
replace the binaries built and is good, but we do not want to install WIX on
all the build VM's)

I have the WIX 3.9 binaries checked into TFS and have that on the build
machine.

So I copied the information from:
http://wixtoolset.org/documentation/manual/v3/msbuild/daily_builds.html

so all my wixproj files have this added:
PropertyGroup
   
WixToolPath$(TLSetupCommonResourcePath)\..\Build\WiX\3.9\/WixToolPath
WixTargetsPath$(WixToolPath)Wix.targets/WixTargetsPath
WixTasksPath$(WixToolPath)wixtasks.dll/WixTasksPath
  /PropertyGroup

and all the MSI's and Bootstrappers (burn) are building :)

However my WIX custom action projects are not building I am getting
errors... so I modified this section:
PropertyGroup
   
WixToolPath$(TLSetupCommonResourcePath)\..\Build\WiX\3.9\sdk\/WixToolPath
WixTargetsPath$(WixToolPath)Wix.targets/WixTargetsPath
WixCATargetsPath$(WixToolPath)Wix.CA.targets/WixCATargetsPath
WixTasksPath$(WixToolPath)wixtasks.dll/WixTasksPath
  /PropertyGroup

since it was complaining it couldn't find the Wix.CA.targets file nor the
deployment/session references :)

I build my custom action project with this:
call %MSBUILD%
C:\Dev\SetupCommon\Main\Source\TitusInstallerCA\TitusInstallerCA.sln
/t:Rebuild /p:Configuration=ReleaseX86 /p:Platform=Mixed Platforms
/l:FileLogger,Microsoft.Build.Engine;logfile=.\Build_Titus_Setup.log;Append


but now getting these two errors:
 Modifying SfxCA.dll stub
EXEC : error : System.IO.FileLoadException: Could not load file or
assembly 'Microsoft.Deployment.Resources, Version=3.0.0.0, Culture=neutral,
PublicKeyToken=ce35f76fcda82bad' or one of its dependencies. The located
assembly's manifest definition does not match the assembly reference.
(Exception from HRESULT: 0x80131040)
File name: 'Microsoft.Deployment.Resources, Version=3.0.0.0,
Culture=neutral, PublicKeyToken=ce35f76fcda82bad'
   at
Microsoft.Deployment.Tools.MakeSfxCA.MakeSfxCA.CopyVersionResource(String
sourceFile, String destFile)
   at Microsoft.Deployment.Tools.MakeSfxCA.MakeSfxCA.Build(String
output, String sfxdll, IList`1 inputs, TextWriter log)
   at Microsoft.Deployment.Tools.MakeSfxCA.MakeSfxCA.Main(String[]
args)

and

EXEC : error : System.IO.FileLoadException: Could not load file or assembly
'Microsoft.Deployment.Resources, Version=3.0.0.0, Culture=neutral,
PublicKeyToken=ce35f76fcda82bad' or one of its dependencies. The located
assembly's manifest definition does not match the assembly reference.
(Exception from HRESULT: 0x80131040)
C:\Dev\SetupCommon\Main\Build\WiX\3.9\sdk\Wix.CA.targets(147,5): error
MSB3073: The command
C:\Dev\SetupCommon\Main\Resources\..\Build\WiX\3.9\sdk\..\sdk\MakeSfxCA.exe
C:\Dev\SetupCommon\Main\Source\TitusInstallerCA\obj\x86\Release\TitusInstaller.CA.dll
C:\Dev\SetupCommon\Main\Resources\..\Build\WiX\3.9\sdk\..\sdk\x86\SfxCA.dll
C:\Dev\SetupCommon\Main\Source\TitusInstallerCA\obj\x86\Release\TitusInstaller.dll
C:\Dev\SetupCommon\Main\Resources\..\Build\WiX\3.9\sdk\Microsoft.Deployment.WindowsInstaller.dll;C:\Dev\StableBuild\GloriaBuilds\Main\TitusEnterprise\Titus.Enterprise.Management.Service\Titus.Common.dll;C:\Dev\StableBuild\GloriaBuilds\Main\TitusEnterprise\Titus.Internal.SetupUtility\Titus.Domain.Types.dll;C:\Dev\StableBuild\GloriaBuilds\Main\TitusEnterprise\Titus.Enterprise.Management.Service\Titus.Enterprise.Management.dll;C:\Dev\StableBuild\GloriaBuilds\Main\TitusEnterprise\Titus.Internal.SetupUtility\Titus.Internal.SetupUtility.dll;C:\Dev\StableBuild\GloriaBuilds\Main\TitusEnterprise\Titus.Enterprise.Management.Service\log4net.dll;C:\Dev\StableBuild\GloriaBuilds\Main\TitusEnterprise\Titus.Enterprise.Management.Service\HtmlAgilityPack.dll;C:\Dev\StableBuild\GloriaBuilds\Main\TitusEnterprise\Titus.Enterprise.Management.Service\NServiceBus.dll;C:\Dev\StableBuild\GloriaBuilds\Main\TitusEnterprise\Titus.Enterprise.Management.Service\Titus.Bus.Messages.dll;C:\Dev\StableBuild\GloriaBuil

[WiX-users] Building WiX Bootstrapper Application with TFS Build

2014-11-24 Thread Yari Serve

Hello,

 

I've created two WiX setups as well as a Bootstrapper that contains both
.msi files inside its Chain. Now I want to build both setups and the BA with
TFS Build.

 

The build itself is successful, I've already moved the WiX sources to TFS
and changed the WiX paths to a relative location in my TFS.

 

Unfortunately, the TFS drop folder contains all of the DLLs and other files
from the build output and not the bootstrapper MSI / exe.

 

How can I do that?

 

Thank you!

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Building Wix 3.6

2013-03-19 Thread Bruce Cran

On 13/03/2013 20:13, jeamis wrote:
 So how do I enlist to the Mercurial repository?   All I want to do is
 compile burn.  I want to confirm our static analysis and debugging.

 Any direction is appreciated.

Clone https://hg.codeplex.com/wix :

hg clone https://hg.codeplex.com/wix -b wix38

To create a build that can be installed on different machines you'll 
need Visual Studio 2008, 2010 and 2012 along with the Visual Studio 
2008, 2010 and 2012 SDKs from the Extensibility Center.  You also need 
HTML Help SDK from 
http://msdn.microsoft.com/en-gb/library/windows/desktop/ms670169(v=vs.85).aspx, 
Sandcastle and Sandcastle Help File Builder from 
http://shfb.codeplex.com/ .  Create a strong name keypair:

sn -k wix.snk
sn -p wix.snk wix.pub
sn -tp wix.pub

Copy the public key and add new InternalsVisibleTo lines in:

src\Votive\sconce\Properties\AssemblyInfo.cs
src\Votive\sdk_vs2010\common\source\csharp\project\AssemblyInfo.cs
src\Votive\sdk_vs2010\common\source\csharp\project\attributes.cs

Then run:

msbuild /p:VisualStudioVersion=11.0 
/p:OFFICIAL_WIX_BUILD=path_to_wix.snk

The binaries will be put in build\debug.  You should also be able to 
open src\Burn.sln and build the projects individually.

-- 
Bruce Cran

--
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_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Building Wix 3.6

2013-03-19 Thread Bruce Cran

On 19/03/2013 12:31, Bruce Cran wrote:
 Clone https://hg.codeplex.com/wix :

 hg clone https://hg.codeplex.com/wix -b wix38

Sorry ignore most of that - those instructions are for WiX 3.8 not 3.6.  
To get 3.6 you just need to use -b wix36 when cloning and follow the 
instructions in the documentation.

-- 
Bruce Cran

--
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_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Building Wix 3.6

2013-03-13 Thread jeamis

Ok, I see that on http://wix.codeplex.com/releases/view/93929 there is a zip
file that contains source.  What is needed to build the wix 3.6 toolkit?

Can I build it using DevStudio 2010?   Is the source complete?   

I tried to open the wix.sln (which my machine says it is 2010 sln file, but
it wants to covert all the sub projects - that does not seem right if it is
a 2010 sln file.

Thanks

Jon





-
- jon
--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Building-Wix-3-6-tp7584313.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_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Building Wix 3.6

2013-03-13 Thread Rob Mensching

You need to enlist in the Mercurial repository to build. The sources.zip is
availble for debugging purposes (along with the pdbs.zip) it is not
buildable. To build wix36, you use make.bat. It requires lots of stuff
installed on your machine to build correctly.

On Wed, Mar 13, 2013 at 11:07 AM, jeamis jonathan.a...@intergraph.comwrote:

Ok, I see that on http://wix.codeplex.com/releases/view/93929 there is a
zip
file that contains source. What is needed to build the wix 3.6 toolkit?

Can I build it using DevStudio 2010? Is the source complete?

I tried to open the wix.sln (which my machine says it is 2010 sln file, but
it wants to covert all the sub projects - that does not seem right if it is
a 2010 sln file.

Thanks

Jon

-
- jon
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Building-Wix-3-6-tp7584313.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_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Building Wix 3.6

2013-03-13 Thread jeamis

Thanks Rob,

So how do I enlist to the Mercurial repository?   All I want to do is
compile burn.  I want to confirm our static analysis and debugging. 

Any direction is appreciated.

-Jon



-
- jon
--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Building-Wix-3-6-tp7584313p7584326.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_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] building Wix

2012-09-12 Thread jaczjill

Rob,

* [property] Target framework changed to Microsoft .NET Framework 2.0. -
NOT SOLVED
* [property] Read-only property dir.hhw cannot be overwritten. - SOLVED
- by removing read-only=true from source code
* [property] Read-only property hhw-found cannot be overwritten. - SOLVED
- by removing read-only=true from source code.

How to solve 1st issue? I am building WiX Source executing MAKE.BAT file
(without any modifications)

In my WIndows 7 system, I have installed following:
1.Microsoft Visual Studio 10.0 Professional
2.Windows SDK for Windows server 2008
3. Microsoft Visual Studio SDK 2010 dot NET framework tools
4. Microsoft SDK for Win 7
5. NANT 0.92
6. Microsoft Visual Studio 2008
7. HTML Help workshot
8. Microsoft Help Viewer 1.0

.NET Frameworks:
Microsoft .NET framework 1.0 SP3 Developer
Microsoft .NET framework 2.0 SP2
Microsoft .NET framework 3.5
Microsoft .NET framework 4 Client Profile
Microsoft .NET framework 4 Extended
Microsoft .NET framework 4 Multi-Targeting Pack

-
jaczjill
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/building-Wix-tp7474266p7580442.html
Sent from the wix-users mailing list archive at Nabble.com.

--
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] building Wix

2012-09-06 Thread jaczjill

I am facing same issue i.e. need to build wixstdba.vcxproj project. If any
one got its solution then please let me know the solution.



-
jaczjill
--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/building-Wix-tp7474266p7580340.html
Sent from the wix-users mailing list archive at Nabble.com.

--
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] building Wix

2012-09-06 Thread Rob Mensching

The WiX v3.6 buid is (unfortunately) wired to build from the beginning and
all the way through. You do have to have the whole environment (lots of
stuff to install) to get there.

On Thu, Sep 6, 2012 at 6:58 AM, jaczjill jaczj...@gmail.com wrote:

I am facing same issue i.e. need to build wixstdba.vcxproj project. If any
one got its solution then please let me know the solution.

-
jaczjill
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/building-Wix-tp7474266p7580340.html
Sent from the wix-users mailing list archive at Nabble.com.

--
virtually,

Rob Mensching
http://RobMensching.com LLC
--
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] Building WiX from source

2012-05-01 Thread Hoover, Jacob

As we now have a 3.6 RC0, I wanted to take another stab at burn.  When I
attempt to build on a clean machine (Win 7 x64) with just VS2010, the
6.1 and 7.1 SDK, and NAnt I keep getting errors like:

 

 

 [exec] Microsoft (R) Build Engine Version 3.5.30729.5420

 [exec] [Microsoft .NET Framework, Version 2.0.50727.5448]

 [exec] Copyright (C) Microsoft Corporation 2007. All rights
reserved.

 [exec]

 [exec] Z:\Projects\wix-36rc0\src\core.sln.cache(301,5): error
MSB4126: The specified solution configuration Debug|AnyCPU is

invalid. Please specify a valid solution configuration using the
Configuration and Platform properties (e.g. MSBuild.exe Solution

.sln /p:Configuration=Debug /p:Platform=Any CPU) or leave those
properties blank to use the default solution configuration.

 

I was also seeing this error from toolsrc.sln.  There I was able to hack
around it by modifying toolsrc.build to include arg
value=/property:Platform=Any CPU / on the toolsrc.inc target, but
this hack doesn't seem to work for the core.  

 

Am I doing something wrong or missing something that is causing this, or
is the current code in HG broken for my specific configuration? I do
believe I have followed all the steps outlined in the help file. I have
also tried every release of Nant from 0.91 up to the bleeding edge with
no success.

 

Any help would be greatly appreciated.

--
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] building Wix

2012-04-17 Thread jean claude klodjan

hello
i'm having problem building wix :

i have installed all the required prerequisites  (or at their equivalent
for Visual 2010)

i basically just would like to build wixstdba, (it requires the balutil.lib
)

- building any project in ext.sln (or in the wix solution) shows
The XsdGen task was not found. Check the following: 1.) The name of the
task in the project file is the same as the name of the task class. 2.) The
task class is public and implements the Microsoft.Build.Framework.ITask
interface. 3.) The task is correctly declared with UsingTask in the
project file, or in the *.tasks files located in the
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319 directory.

- building using make shows
* Buildfile: file:///D:/Projets/wix sources/wix.build
* Target framework: Microsoft .NET Framework 4.0
* Target(s) specified: inc
*
*  [property] Target framework changed to Microsoft .NET Framework 2.0.
*  [property] Read-only property dir.hhw cannot be overwritten.
*  [property] Read-only property hhw-found cannot be overwritten.
*
* BUILD FAILED - 0 non-fatal error(s), 2 warning(s)

what do i miss ?
thank you in advance
--
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] building Wix

2012-04-17 Thread Neil Sleightholm

It can be done but you need to unwire all the wix build customisations before 
it will work - personally I have found none of solutions in the wix source work 
unless you can first build everything and even then it is not easy. What I did 
to build wixstdba was pull out the projects wixstdba and balutil in to their 
own solution and then rewire the include and lib files to reference the wix 3.6 
sdk in C:\Program Files\WiX Toolset v3.6\SDK (this is probably how the 
developers expected it to work). I have not been able to get the extension or 
wixlib to build but just creating wixstdba was enough for me.

Hope this helps.

Neil

-Original Message-
From: jean claude klodjan [mailto:jcklod...@gmail.com] 
Sent: 17 April 2012 18:27
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] building Wix

hello
i'm having problem building wix :

i have installed all the required prerequisites  (or at their equivalent for 
Visual 2010)

i basically just would like to build wixstdba, (it requires the balutil.lib
)

- building any project in ext.sln (or in the wix solution) shows The XsdGen 
task was not found. Check the following: 1.) The name of the task in the 
project file is the same as the name of the task class. 2.) The task class is 
public and implements the Microsoft.Build.Framework.ITask interface. 3.) The 
task is correctly declared with UsingTask in the project file, or in the 
*.tasks files located in the C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319 
directory.

- building using make shows
* Buildfile: file:///D:/Projets/wix sources/wix.build
* Target framework: Microsoft .NET Framework 4.0
* Target(s) specified: inc
*
*  [property] Target framework changed to Microsoft .NET Framework 2.0.
*  [property] Read-only property dir.hhw cannot be overwritten.
*  [property] Read-only property hhw-found cannot be overwritten.
*
* BUILD FAILED - 0 non-fatal error(s), 2 warning(s)

what do i miss ?
thank you in advance
--
Better than sec? Nothing is better than sec when it comes to monitoring Big 
Data applications. Try Boundary one-second resolution app monitoring today. 
Free.
http://p.sf.net/sfu/Boundary-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Building wix from visual studio 2008 using HeatDirectory/HeatTask

2009-04-21 Thread Brian Bakkebo

OK, Brian I am back again with a new question.  Been Digging around the wix
code. :)
Now I have tried out Project harvester and the problem is I cannot get in
all the dll's included with the project.  Basically we have multiple
projects in the solution.  So I tried to use the
Satellites ProjectOutputGroup which I think would do the trick, but it is
not working for me(I probably am doing it wrong, but tried command line also
and no output).  So basically all I get out is the projects .exe file
outputed.  Really what I need is all the output from the solution file.   So
I was thinking that I probably have to use heatdirectory again.

Here is the wix.proj file and the output so you can better see:
Thanks for your help.

Project DefaultTargets=Build xmlns=
http://schemas.microsoft.com/developer/msbuild/2003;
  PropertyGroup
Configuration Condition= '$(Configuration)' == ''
Debug/Configuration
Platform Condition= '$(Platform)' == '' x86/Platform
ProductVersion1.0/ProductVersion
ProjectGuid{1bc4cf27-badd-47e0-87a7-9e3ed0c8c50b}/ProjectGuid
SchemaVersion2.0/SchemaVersion
OutputNameWix_TagImport/OutputName
OutputTypePackage/OutputType
WixToolPath..\..\DLL\Wix\/WixToolPath
WixTasksPath$(WixToolPath)\wixtasks.dll/WixTasksPath
WixTargetsPath$(WixToolPath)\Wix.targets/WixTargetsPath
  /PropertyGroup
  PropertyGroup
Configuration Condition= '$(Configuration)' ==
''Debug/Configuration
OutputNamemsbuild.heatfile/OutputName
OutputTypePackage/OutputType
WixToolPath..\..\DLL\Wix\/WixToolPath
Culturesen-us/Cultures
LinkerBaseInputPaths..\..\DLL\Wix\/LinkerBaseInputPaths
  /PropertyGroup
   ItemGroup
   Compile Include=Components.wxs /
 /ItemGroup
  Import Project=$(WixToolPath)\Wix.targets /
  UsingTask TaskName=HeatProject
AssemblyFile=$(WixToolPath)WixUtilExtension.dll /
  Target Name=BeforeBuild
HeatProject

Project=..\PrestigeTagImportStandaloneHost\PrestigeTagImportStandaloneHost.csproj
   ProjectOutputGroups=Binaries
   OutputFile=Components.wxs
   AutogenerateGuids=true
   ToolPath=$(WixToolPath)/
  /Target
UsingTask TaskName=HeatProject
AssemblyFile=$(WixToolPath)WixUtilExtension.dll /
  Target Name=BeforeBuild
HeatProject

Project=..\PrestigeTagImportStandaloneHost\PrestigeTagImportStandaloneHost.csproj
   ProjectOutputGroups=Satellites
   OutputFile=Components2.wxs
   AutogenerateGuids=true
   ToolPath=$(WixToolPath)/
  /Target
  PropertyGroup Condition= '$(Configuration)|$(Platform)' == 'Debug|x86'

OutputPathbin\$(Configuration)\/OutputPath
IntermediateOutputPathobj\$(Configuration)\/IntermediateOutputPath
DefineConstantsDebug/DefineConstants
  /PropertyGroup
  PropertyGroup Condition= '$(Configuration)|$(Platform)' == 'Release|x86'

OutputPathbin\$(Configuration)\/OutputPath
IntermediateOutputPathobj\$(Configuration)\/IntermediateOutputPath
  /PropertyGroup
  ItemGroup
WixExtension Include=WixUtilExtension
  HintPath$(WixToolPath)\WixUtilExtension.dll/HintPath
/WixExtension
WixExtension Include=WixUIExtension
  HintPath$(WixToolPath)\WixUIExtension.dll/HintPath
/WixExtension
  /ItemGroup
  ItemGroup
Compile Include=WixUI_Minimal_NoLicense.wxs /
Compile Include=Wix_TagImport.wxs /
  /ItemGroup
  Import Project=$(WixTargetsPath) /
  !--
To modify your build process, add your task inside one of the targets below
and uncomment it.
Other similar extension points exist, see Wix.targets.
Target Name=BeforeBuild
/Target
Target Name=AfterBuild
/Target
--
/Project

?xml version=1.0 encoding=utf-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Fragment
DirectoryRef Id=PrestigeTagImportStandaloneHost.Binaries
Component Id=cmp8F5D22A8483B0DE94482B3AD5BDB74BF Guid=*
File Id=filDDCC5FCC7A0DD48047950A8F4CBA3DA5
Source=$(var.PrestigeTagImportStandaloneHost.TargetDir)\PrestigeTagImportStandaloneHost.exe
/
/Component
/DirectoryRef
/Fragment
Fragment
ComponentGroup Id=PrestigeTagImportStandaloneHost.Binaries
ComponentRef Id=cmp8F5D22A8483B0DE94482B3AD5BDB74BF /
/ComponentGroup
/Fragment
/Wix


2009/4/20 Brian Bakkebo bbakk...@gmail.com

 Thanks Brian I am using the latest drop of wix.

 Brian, no I didn't know about the project harvester. That is basically what
 I am trying to do.  Is there any info on how to use it anywhere?

 On Apr 20, 2009 5:38 PM, Brian Rogers rogers.br...@gmail.com wrote:

 Hey Brian,

 Which version of heat.exe are you using? Is it this weeks drop? Second, if
 you could show more or your source wixproj that would be great. Also, the
 PreprocessorVariable takes only var.MyVar not $(var.MyVar).

 Do you know about the VSProject harvestor extension? This might work for
 what you are doing. Check it out heat.exe -? and look for project.

 Thanks, Brian Rogers Intelligence removes complexity. - Me
 http://icumove.spaces.live.com

 On Mon, Apr 20, 2009 at 7:51

Re: [WiX-users] Building wix from visual studio 2008 using HeatDirectory/HeatTask

2009-04-21 Thread Brian Rogers

Hey Brian,

Am I understanding you correctly when you say you have dependency .dlls
listed in the project itself? If that is the case you could create a
separate call to heat.exe to get those files as individuals. Unfortunately
the only other way I know how to do this would be to use the -pog:Sources
switch. However, this will give you ALL the source code and I don't think
that is what you are looking for.

Brian Rogers
Intelligence removes complexity. - Me
http://icumove.spaces.live.com


On Tue, Apr 21, 2009 at 3:55 AM, Brian Bakkebo bbakk...@gmail.com wrote:

 OK, Brian I am back again with a new question.  Been Digging around the wix
 code. :)
 Now I have tried out Project harvester and the problem is I cannot get in
 all the dll's included with the project.  Basically we have multiple
 projects in the solution.  So I tried to use the
 Satellites ProjectOutputGroup which I think would do the trick, but it is
 not working for me(I probably am doing it wrong, but tried command line
 also
 and no output).  So basically all I get out is the projects .exe file
 outputed.  Really what I need is all the output from the solution file.
 So
 I was thinking that I probably have to use heatdirectory again.

 Here is the wix.proj file and the output so you can better see:
 Thanks for your help.

 Project DefaultTargets=Build xmlns=
 http://schemas.microsoft.com/developer/msbuild/2003;
   PropertyGroup
Configuration Condition= '$(Configuration)' == ''
 Debug/Configuration
 Platform Condition= '$(Platform)' == '' x86/Platform
ProductVersion1.0/ProductVersion
ProjectGuid{1bc4cf27-badd-47e0-87a7-9e3ed0c8c50b}/ProjectGuid
SchemaVersion2.0/SchemaVersion
OutputNameWix_TagImport/OutputName
OutputTypePackage/OutputType
 WixToolPath..\..\DLL\Wix\/WixToolPath
WixTasksPath$(WixToolPath)\wixtasks.dll/WixTasksPath
WixTargetsPath$(WixToolPath)\Wix.targets/WixTargetsPath
  /PropertyGroup
   PropertyGroup
Configuration Condition= '$(Configuration)' ==
 ''Debug/Configuration
OutputNamemsbuild.heatfile/OutputName
OutputTypePackage/OutputType
 WixToolPath..\..\DLL\Wix\/WixToolPath
Culturesen-us/Cultures
LinkerBaseInputPaths..\..\DLL\Wix\/LinkerBaseInputPaths
  /PropertyGroup
   ItemGroup
   Compile Include=Components.wxs /
  /ItemGroup
  Import Project=$(WixToolPath)\Wix.targets /
   UsingTask TaskName=HeatProject
 AssemblyFile=$(WixToolPath)WixUtilExtension.dll /
  Target Name=BeforeBuild
 HeatProject


 Project=..\PrestigeTagImportStandaloneHost\PrestigeTagImportStandaloneHost.csproj
   ProjectOutputGroups=Binaries
   OutputFile=Components.wxs
AutogenerateGuids=true
   ToolPath=$(WixToolPath)/
  /Target
 UsingTask TaskName=HeatProject
 AssemblyFile=$(WixToolPath)WixUtilExtension.dll /
  Target Name=BeforeBuild
 HeatProject


 Project=..\PrestigeTagImportStandaloneHost\PrestigeTagImportStandaloneHost.csproj
   ProjectOutputGroups=Satellites
   OutputFile=Components2.wxs
AutogenerateGuids=true
   ToolPath=$(WixToolPath)/
  /Target
   PropertyGroup Condition= '$(Configuration)|$(Platform)' == 'Debug|x86'
 
OutputPathbin\$(Configuration)\/OutputPath
IntermediateOutputPathobj\$(Configuration)\/IntermediateOutputPath
DefineConstantsDebug/DefineConstants
  /PropertyGroup
  PropertyGroup Condition= '$(Configuration)|$(Platform)' == 'Release|x86'
 
OutputPathbin\$(Configuration)\/OutputPath
IntermediateOutputPathobj\$(Configuration)\/IntermediateOutputPath
  /PropertyGroup
  ItemGroup
WixExtension Include=WixUtilExtension
  HintPath$(WixToolPath)\WixUtilExtension.dll/HintPath
/WixExtension
WixExtension Include=WixUIExtension
  HintPath$(WixToolPath)\WixUIExtension.dll/HintPath
/WixExtension
  /ItemGroup
  ItemGroup
Compile Include=WixUI_Minimal_NoLicense.wxs /
Compile Include=Wix_TagImport.wxs /
  /ItemGroup
  Import Project=$(WixTargetsPath) /
  !--
 To modify your build process, add your task inside one of the targets below
 and uncomment it.
 Other similar extension points exist, see Wix.targets.
 Target Name=BeforeBuild
 /Target
 Target Name=AfterBuild
 /Target
 --
 /Project

 ?xml version=1.0 encoding=utf-8?
 Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Fragment
DirectoryRef Id=PrestigeTagImportStandaloneHost.Binaries
Component Id=cmp8F5D22A8483B0DE94482B3AD5BDB74BF Guid=*
File Id=filDDCC5FCC7A0DD48047950A8F4CBA3DA5

 Source=$(var.PrestigeTagImportStandaloneHost.TargetDir)\PrestigeTagImportStandaloneHost.exe
 /
/Component
/DirectoryRef
/Fragment
Fragment
ComponentGroup Id=PrestigeTagImportStandaloneHost.Binaries
ComponentRef Id=cmp8F5D22A8483B0DE94482B3AD5BDB74BF /
/ComponentGroup
/Fragment
 /Wix


 2009/4/20 Brian Bakkebo bbakk...@gmail.com

  Thanks Brian I am using the latest drop of wix.
 
  Brian, no I didn't know about the project harvester. That is basically
 what

Re: [WiX-users] Building wix from visual studio 2008 using HeatDirectory/HeatTask

2009-04-21 Thread Brian Bakkebo

Thanks for the answer Brian.

Yes, its very basic and ugly for some of our apps.  I am working on that as
well.
What would be ideal is if you could just specify the .sln file and then heat
automagically fetched all the structure plus reference dlls.  That would
be the dream..Perhaps version 4.0 of wix!  ...Of course you would need to
include all the best practices for component rules(a lot of this is there),
windows installer rules, etc, baked in and then wix plus heat has become
basically the autopilot installer, well not quite, but close. :)

I looked at Sources and it will not work.  Too many files there.. So, I am
back to heatdirectory now as it appears to do what I need.

Thanks for all your help
Brian




2009/4/21 Brian Rogers rogers.br...@gmail.com

 Hey Brian,

 Am I understanding you correctly when you say you have dependency .dlls
 listed in the project itself? If that is the case you could create a
 separate call to heat.exe to get those files as individuals. Unfortunately
 the only other way I know how to do this would be to use the -pog:Sources
 switch. However, this will give you ALL the source code and I don't think
 that is what you are looking for.

 Brian Rogers
 Intelligence removes complexity. - Me
 http://icumove.spaces.live.com


 On Tue, Apr 21, 2009 at 3:55 AM, Brian Bakkebo bbakk...@gmail.com wrote:

  OK, Brian I am back again with a new question.  Been Digging around the
 wix
  code. :)
  Now I have tried out Project harvester and the problem is I cannot get in
  all the dll's included with the project.  Basically we have multiple
  projects in the solution.  So I tried to use the
  Satellites ProjectOutputGroup which I think would do the trick, but it
 is
  not working for me(I probably am doing it wrong, but tried command line
  also
  and no output).  So basically all I get out is the projects .exe file
  outputed.  Really what I need is all the output from the solution file.
  So
  I was thinking that I probably have to use heatdirectory again.
 
  Here is the wix.proj file and the output so you can better see:
  Thanks for your help.
 
  Project DefaultTargets=Build xmlns=
  http://schemas.microsoft.com/developer/msbuild/2003;
PropertyGroup
 Configuration Condition= '$(Configuration)' == ''
  Debug/Configuration
  Platform Condition= '$(Platform)' == '' x86/Platform
 ProductVersion1.0/ProductVersion
 ProjectGuid{1bc4cf27-badd-47e0-87a7-9e3ed0c8c50b}/ProjectGuid
 SchemaVersion2.0/SchemaVersion
 OutputNameWix_TagImport/OutputName
 OutputTypePackage/OutputType
  WixToolPath..\..\DLL\Wix\/WixToolPath
 WixTasksPath$(WixToolPath)\wixtasks.dll/WixTasksPath
 WixTargetsPath$(WixToolPath)\Wix.targets/WixTargetsPath
   /PropertyGroup
PropertyGroup
 Configuration Condition= '$(Configuration)' ==
  ''Debug/Configuration
 OutputNamemsbuild.heatfile/OutputName
 OutputTypePackage/OutputType
  WixToolPath..\..\DLL\Wix\/WixToolPath
 Culturesen-us/Cultures
 LinkerBaseInputPaths..\..\DLL\Wix\/LinkerBaseInputPaths
   /PropertyGroup
ItemGroup
Compile Include=Components.wxs /
   /ItemGroup
   Import Project=$(WixToolPath)\Wix.targets /
UsingTask TaskName=HeatProject
  AssemblyFile=$(WixToolPath)WixUtilExtension.dll /
   Target Name=BeforeBuild
  HeatProject
 
 
 
 Project=..\PrestigeTagImportStandaloneHost\PrestigeTagImportStandaloneHost.csproj
ProjectOutputGroups=Binaries
OutputFile=Components.wxs
 AutogenerateGuids=true
ToolPath=$(WixToolPath)/
   /Target
  UsingTask TaskName=HeatProject
  AssemblyFile=$(WixToolPath)WixUtilExtension.dll /
   Target Name=BeforeBuild
  HeatProject
 
 
 
 Project=..\PrestigeTagImportStandaloneHost\PrestigeTagImportStandaloneHost.csproj
ProjectOutputGroups=Satellites
OutputFile=Components2.wxs
 AutogenerateGuids=true
ToolPath=$(WixToolPath)/
   /Target
PropertyGroup Condition= '$(Configuration)|$(Platform)' ==
 'Debug|x86'
  
 OutputPathbin\$(Configuration)\/OutputPath
 IntermediateOutputPathobj\$(Configuration)\/IntermediateOutputPath
 DefineConstantsDebug/DefineConstants
   /PropertyGroup
   PropertyGroup Condition= '$(Configuration)|$(Platform)' ==
 'Release|x86'
  
 OutputPathbin\$(Configuration)\/OutputPath
 IntermediateOutputPathobj\$(Configuration)\/IntermediateOutputPath
   /PropertyGroup
   ItemGroup
 WixExtension Include=WixUtilExtension
   HintPath$(WixToolPath)\WixUtilExtension.dll/HintPath
 /WixExtension
 WixExtension Include=WixUIExtension
   HintPath$(WixToolPath)\WixUIExtension.dll/HintPath
 /WixExtension
   /ItemGroup
   ItemGroup
 Compile Include=WixUI_Minimal_NoLicense.wxs /
 Compile Include=Wix_TagImport.wxs /
   /ItemGroup
   Import Project=$(WixTargetsPath) /
   !--
  To modify your build process, add your task inside one of the targets
 below
  and uncomment it.
  Other similar extension points exist, see Wix.targets.
  Target

Re: [WiX-users] Building wix from visual studio 2008 using HeatDirectory/HeatTask

2009-04-20 Thread Brian Bakkebo

Hello Brian, thanks for your response below. It solved just about
everything for me. Now I have a problem with the heat output:
File Id=filECAD2FA36BABE7788C7D38952DE30E56 KeyPath=yes
Source=SourceDir\
So I tried to do this here:
Adding this:
HeatDirectory
PreprocessorVariable=$(var.MyVar)
.../
based on your heat examples here:
http://icumove.spaces.live.com/blog/cns!FB93073C6534B681!461.entry

But I am not quite sure how to define this variable in the wix project file
or if I can?
What I am trying to do is have this point to my output directory ie:Debug or
Release\
Can you give me an idea of what I need to do here.

Med vennlig hilsen /Regards
Brian

2009/4/19 Brian Rogers rogers.br...@gmail.com

Hey Brian,

Try the below.

PropertyGroup
Configuration Condition= '$(Configuration)' == ''
Debug/Configuration
OutputNamemsbuild.heatfile/OutputName
OutputTypePackage/OutputType
WixToolPath*Pass via the command line*/WixToolPath
Culturesen-us/Cultures
LinkerBaseInputPaths..\..\data\HeatDir/LinkerBaseInputPaths
/PropertyGroup
ItemGroup
Compile Include=product.wxs /
Compile Include=TestDir.wxs /
/ItemGroup
Import Project=$(WixToolPath)\Wix.targets /
UsingTask TaskName=HeatDirectory
AssemblyFile=$(WixToolPath)WixUtilExtension.dll /
Target Name=BeforeBuild
HeatDirectory
Directory=..\..\data\HeatDir
DirectoryRefId=DataDir
OutputFile=TestDir.wxs
AutogenerateGuids=true
ToolPath=$(WixToolPath) /
/Target

Thanks,

Brian Rogers
Intelligence removes complexity. - Me
http://icumove.spaces.live.com

On Sun, Apr 19, 2009 at 5:39 AM, Brian Bakkebo bbakk...@gmail.com wrote:

Hello all (I posted this to the wrong list on friday(wix-users-request))

Rob pointed out to me that there was a way to use heattasks:

http://stackoverflow.com/questions/710687/best-way-to-create-a-wix-fragment-file-based-on-user-defined-directories-to-be-us,but
I have not been able to get heattask or heatdirectory to work after
trying
different methods.

I found a much earlier post on the mailing-list here stating that you can
use this a command like this in the wixproj file below to get
HeatDirectory
to work:

WixToolPath..\..\DLL\Wix\/WixToolPath
WixTasksPath$(WixToolPath)\wixtasks.dll/WixTasksPath
WixTargetsPath$(WixToolPath)\Wix.targets/WixTargetsPath
/PropertyGroup

Target Name=BeforeBuild
HeatDirectory Directory=..\..\DLL\Wix\ OutputFile=test.wxs
GenerateGuidsNow=true SuppressFragments=true Template=module
ToolPath=$(WixToolPath) /
/Target

The build succeeds, but I am not seeing any file output and no mention of
heat running in the output in vs. I also tried msbuild same results...

1. Can someone give me proper syntax for this to run from a Visual studio
wix project for the HeatDirectory and a HeatTask commands?

I could not find any documentation on this, perhaps this would help out
as
well. I will update my post to stackoverflow when I get this all worked
out,
to share the infor.

Thanks in advance for your help.

I can provide my full .wixproj if it is needed

Thanks in advance

Brian

--
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Building wix from visual studio 2008 using HeatDirectory/HeatTask

2009-04-20 Thread Brian Rogers

Hey Brian,

Which version of heat.exe are you using? Is it this weeks drop? Second, if
you could show more or your source wixproj that would be great. Also, the
PreprocessorVariable takes only var.MyVar not $(var.MyVar).

Do you know about the VSProject harvestor extension? This might work for
what you are doing. Check it out heat.exe -? and look for project.

Thanks,

Brian Rogers
Intelligence removes complexity. - Me
http://icumove.spaces.live.com

On Mon, Apr 20, 2009 at 7:51 AM, Brian Bakkebo bbakk...@gmail.com wrote:

But I am not quite sure how to define this variable in the wix project file
or if I can?
What I am trying to do is have this point to my output directory ie:Debug
or
Release\
Can you give me an idea of what I need to do here.

Med vennlig hilsen /Regards
Brian

2009/4/19 Brian Rogers rogers.br...@gmail.com

Hey Brian,

Try the below.

Thanks,

Brian Rogers
Intelligence removes complexity. - Me
http://icumove.spaces.live.com

On Sun, Apr 19, 2009 at 5:39 AM, Brian Bakkebo bbakk...@gmail.com
wrote:

Hello all (I posted this to the wrong list on
friday(wix-users-request))

Rob pointed out to me that there was a way to use heattasks:

I found a much earlier post on the mailing-list here stating that you
can
use this a command like this in the wixproj file below to get
HeatDirectory
to work:

WixToolPath..\..\DLL\Wix\/WixToolPath
WixTasksPath$(WixToolPath)\wixtasks.dll/WixTasksPath
WixTargetsPath$(WixToolPath)\Wix.targets/WixTargetsPath
/PropertyGroup

Target Name=BeforeBuild
HeatDirectory Directory=..\..\DLL\Wix\ OutputFile=test.wxs
GenerateGuidsNow=true SuppressFragments=true Template=module
ToolPath=$(WixToolPath) /
/Target

The build succeeds, but I am not seeing any file output and no mention
of
heat running in the output in vs. I also tried msbuild same results...

1. Can someone give me proper syntax for this to run from a Visual
studio
wix project for the HeatDirectory and a HeatTask commands?

I could not find any documentation on this, perhaps this would help out
as
well. I will update my post to stackoverflow when I get this all worked
out,
to share the infor.

Thanks in advance for your help.

I can provide my full .wixproj if it is needed

Thanks in advance

Brian

Re: [WiX-users] Building wix from visual studio 2008 using HeatDirectory/HeatTask

2009-04-20 Thread Brian Bakkebo

Thanks Brian I am using the latest drop of wix.

Brian, no I didn't know about the project harvester. That is basically what
I am trying to do.  Is there any info on how to use it anywhere?

On Apr 20, 2009 5:38 PM, Brian Rogers rogers.br...@gmail.com wrote:

Hey Brian,

Which version of heat.exe are you using? Is it this weeks drop? Second, if
you could show more or your source wixproj that would be great. Also, the
PreprocessorVariable takes only var.MyVar not $(var.MyVar).

Do you know about the VSProject harvestor extension? This might work for
what you are doing. Check it out heat.exe -? and look for project.

Thanks, Brian Rogers Intelligence removes complexity. - Me
http://icumove.spaces.live.com

On Mon, Apr 20, 2009 at 7:51 AM, Brian Bakkebo bbakk...@gmail.com wrote: 
Hello Brian, thanks fo...
 http://icumove.spaces.live.com/blog/cns!FB93073C6534B681!461.entry
http://icumove.spaces.live.com/blog/cns%21FB93073C6534B681%21461.entry

  But I am not quite sure how to define this variable in the wix project
file  or if I can?  Wha...
--
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Building wix from visual studio 2008 using HeatDirectory/HeatTask

2009-04-19 Thread Brian Bakkebo

Hello all (I posted this to the wrong list on friday(wix-users-request))

Rob pointed out to me that there was a way to use heattasks:
http://stackoverflow.com/questions/710687/best-way-to-create-a-wix-fragment-file-based-on-user-defined-directories-to-be-us,but
I have not been able to get heattask or heatdirectory to work after trying
different methods.

I found a much earlier post on the mailing-list here stating that you can
use this a command like this in the wixproj file below to get HeatDirectory
to work:

WixToolPath..\..\DLL\Wix\/WixToolPath
WixTasksPath$(WixToolPath)\wixtasks.dll/WixTasksPath
WixTargetsPath$(WixToolPath)\Wix.targets/WixTargetsPath
/PropertyGroup

Target Name=BeforeBuild
HeatDirectory Directory=..\..\DLL\Wix\ OutputFile=test.wxs
GenerateGuidsNow=true SuppressFragments=true Template=module
ToolPath=$(WixToolPath) /
/Target

The build succeeds, but I am not seeing any file output and no mention of
heat running in the output in vs. I also tried msbuild same results...

1. Can someone give me proper syntax for this to run from a Visual studio
wix project for the HeatDirectory and a HeatTask commands?

I could not find any documentation on this, perhaps this would help out as
well. I will update my post to stackoverflow when I get this all worked out,
to share the infor.

Thanks in advance for your help.

I can provide my full .wixproj if it is needed

Thanks in advance

Brian
--
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Building wix from visual studio 2008 using HeatDirectory/HeatTask

2009-04-19 Thread Brian Rogers