I finally figured it out.
The of the build file needs to be set to 'Bundle' and I also
need to include the WixBalExtension using the element.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/MSBUILD-and-Burn-tp7592535p7592592.html
Sent from the
inked.
> Date: Sun, 25 Aug 2013 13:48:19 -0700
> From: phogl...@rimage.com
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] MSBuild wix project file - how to detect skipped and
> specific culture
>
> Is there a MSBuild Task or a method of conditioning one of the Tar
Is there a MSBuild Task or a method of conditioning one of the Targets that
fires prior to Compile, so that my in-line task will not fire if linking is
going to be skipped?
I notice that when I add a task to Target MsiSign that it does not file if
linking is skipped (which is the behavior that I w
Hi,
I already posted this question in the msbuild forum, but maybe there are WIX
developers still using the msbuild-GenerateBootstrapper approach who know an
answer to this...
I'm using the GenerateBootstrapper-task to create a bootstrapper for a WIX
setup project. Among other things this bootstr
Harvesting was disabled in WiX v3.6 because there were so many issues in it.
On Sat, Nov 26, 2011 at 3:59 PM, David P. Romig, Sr. wrote:
> My WiX VS 2010 project contains direct file references (i.e. template
> files) and project references. In the WiX project, each of the .NET
> project refere
My WiX VS 2010 project contains direct file references (i.e. template
files) and project references. In the WiX project, each of the .NET
project references has the property Harvest="true" and Project Output
Groups="Binaries".
When building the WiX project (or the entire solution), whether in the
h the
workflow-based build process template) in 2010.
-Original Message-
From: Michael Stoll [mailto:unwicht...@mistoll.de]
Sent: Thursday, June 02, 2011 1:09 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] MSBuild project references and multiple pl
AFAIK this is not possible.
I did something like that by modifiying the msbuild process using two
'msbuild' tasks (http://msdn.microsoft.com/en-us/library/z7f65y0d.aspx)
for building the x64 and the x86 platform dependencies.
Michael
Am 02.06.2011 19:54, schrieb Randy Johnson:
> Hi,
>
> I have
Hi,
I have a question about using MSBuild and including multiple platforms (i.e.
32-bit and 64-bit) of the *same* component in an msi. Using Visual Studio I can
add a project references from my WIX project to any dependent project (C# class
library, etc.) and it will be built first. So for inst
Thanks Rob
For now, I've worked around it by adding a custom step in the AfterBuild
target to copy the MSIs.
Jacques
On Thu, Feb 24, 2011 at 7:10 AM, Rob Mensching wrote:
> I *think* the change came when the new tool to sign cabinets came in. I'm
> looking at this code right now myself. I'm wo
I *think* the change came when the new tool to sign cabinets came in. I'm
looking at this code right now myself. I'm wondering if there is a bug in
here somewhere. I'll let you know if I find anything interesting.
On Mon, Feb 21, 2011 at 3:59 PM, Jacques Eloff wrote:
> Hi
>
> I rely on batching
Hi
I rely on batching to generate multiple sets of MSIs from the same wixproj
files. The files are generated to the same output location, but are
different based on properities I pass to the wixproj files that control
thigns like the MSI name, etc. I'd typically invoke the project as follows
Wi
for updating the WiX installer version number
information.
-Original Message-
From: Adam Burton [mailto:adz...@gmail.com]
Sent: Thursday, December 02, 2010 1:40 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] msbuild variables in wix source files
On Thursday 02 Dec 2010
-
From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk]
Sent: Thursday, December 02, 2010 11:00 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] msbuild variables in wix source files
Hi:
Is it possible to use msbuild variables (such as $(configuration)) in a .wxs
source
On Thursday 02 Dec 2010 18:59:37 Sean Farrow wrote:
> Hi:
> Is it possible to use msbuild variables (such as $(configuration)) in a
> .wxs source file? Any help appreciated.
> Cheers
> Sean.
> ---
> --- Increase Visibility of Y
You need to pass in the VS variable value on the WiX project's "command
line", by doing something like this:
In the build properties for your WiX project, you can define preprocessor
variables, and there you could specify something like
MYCONFIG=$(Configuration)
Then you can test the MYCONFIG va
Hi:
Is it possible to use msbuild variables (such as $(configuration)) in a .wxs
source file?
Any help appreciated.
Cheers
Sean.
--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest
Switching the TFS Build 2010 process to 32 bit indeed solved the
issue. No more exceptions. Now the issue is that its MSBuild 4.0 and
TFS Build 2010 is building the .wixproj before the .csproj it is
referencing. That is not going to work right. However, that is going
to have to be a new thread
ilto:krjon...@aye.net]
>Sent: 28 October 2010 00:19
>To: wix-users@lists.sourceforge.net
>Subject: [WiX-users] MSBuild Wix Compile Task Throwing Exception
>
>
>This one has me stumped, I'm getting the following exception on a
>TfsBuild 2008 server from the compile wix MSBuil
Thanks Nick for your time. The picture is getting clearer.
Yes, I do intend buy this book but in ebook format to start off with.
Satesh
From: Nick Ramirez [via Windows Installer XML (WiX) toolset]
[mailto:ml-node+5682799-1873990454-298...@n2.nabble.com]
Sent: T
So, it sounds like you're trying to create an installer, but have recent
builds of your product incorporated in automatically? A sort of
constant-integration installer?
I think you may be on the right track by using Heat. It's a good tool for
generating a WiX source file for you. You probably al
19
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] MSBuild Wix Compile Task Throwing Exception
This one has me stumped, I'm getting the following exception on a
TfsBuild 2008 server from the compile wix MSBuild task:
Could not load file or assembly 'file:///c:\BTemp\Rx Prod
This one has me stumped, I'm getting the following exception on a
TfsBuild 2008 server from the compile wix MSBuild task:
Could not load file or assembly 'file:///c:\BTemp\Rx Production
Applications\RxAuditCreatorServer_Dev2\Sources\wix\candle.exe' or one
of its dependencies. An attempt was
I managed to understand the usage of HEAT and i saw the output of that tool
is to a wxs file which changes the structure with in. Since i am just
starting to use wix, pardon my understanding. As i understand, i have a wxs
file and the heat tool also outputs to wxs file. my question is Should i be
Hi,
my project is developed in 32 bit machine,
when i build my project for 32 bit platform using msbuild(target files),
msbuild builds successfully,
but if i try to build the same project to 64 bit machine,
its throwing the following warnings
Warning CS1607: Assembly generation -- Refe
yes it is possible t change the password.
you need to tweak the configuration file and set authentication to use mixed
mode.
Refer to the following msdn page find the parameters you need to change
http://msdn.microsoft.com/en-us/library/ms144259.aspx
Regards,
Asiri Wanigarathne
On 16 May 2010 0
References:
<1827ffb9db064245b9b10727dadf43401681556...@iwpmail1.corp.checkfree.com><1827ffb9db064245b9b10727dadf434016815f0...@iwpmail1.corp.checkfree.com><1827ffb9db064245b9b10727dadf434016815f1...@iwpmail1.corp.checkfree.com><1827ffb9db064245b9b10727dadf434016815f1...@iwpmail1.corp.checkfre
References:
<1827ffb9db064245b9b10727dadf43401681556...@iwpmail1.corp.checkfree.com><1827ffb9db064245b9b10727dadf434016815f0...@iwpmail1.corp.checkfree.com><1827ffb9db064245b9b10727dadf434016815f1...@iwpmail1.corp.checkfree.com><1827ffb9db064245b9b10727dadf434016815f1...@iwpmail1.corp.checkfre
...@fiserv.com]
Sent: Thursday, May 20, 2010 11:48 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] msbuild command line parameters
Sweet! That write-up was extremely useful! Steps 1-3 gave me the context I
needed. Thank you so very much! I was probably being
E�ޭ��z�w�~D�nE�M4�/8��A�;�_<ӝ5�к�,��{)yhq�A���]��4Ӏ�㾵���|�Nt�_B��3*�r���ƥ�5�P��@@�v ��...@�
��Ja��7�Mv�^�N:Ӿ���9�]} �5�*'�'���_6�QA�0t델� A�N��0���^�מz�>HX�
�\��\��$~��r�]��4Ӏ�㾵���|�Nt�_B� s*�r���ƥ�ͻP} :�n9�uӽ�
��~4ׯ5�]B<�/W(��!y� �眢`w�~D�nE
Please consider the environment before printing this e-mail
> -Original Message-
> From: Kurt Jensen [mailto:kurt.jen...@ophir-spiricon.com]
> Sent: Thursday, May 20, 2010 10:06 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] msbuild c
Thursday, May 20, 2010 7:34 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] msbuild command line parameters
>
> OK. I have a much easier repro scenario. I tried simply running msbuild on
> my tfsbuild.proj
> (after all this time
olset.
Subject: Re: [WiX-users] msbuild command line parameters
What does your TFS build file look like? I don't have TFS but I have used it in
the past. I'll do the best I can.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fa
ll do not see
BGProductName in the build log or on the command line.
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, May 19, 2010 1:37 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] msbuild co
discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] msbuild command line parameters
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
e printing this e-mail
> -Original Message-
> From: Kurt Jensen [mailto:kurt.jen...@ophir-spiricon.com]
> Sent: Wednesday, May 19, 2010 12:19 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] msbuild command line parameters
>
>
sage-
> From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
> Sent: Wednesday, May 19, 2010 11:29 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] msbuild command line parameters
>
> Caveat: I don't have a TFS environment
mailto:edwin.cas...@fiserv.com]
> Sent: Wednesday, May 19, 2010 11:29 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] msbuild command line parameters
>
> Caveat: I don't have a TFS environment to test this out on.
>
> I created a new Wi
- 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: Kurt Jensen [mailto:kurt.jen...@ophir-spiricon.com]
> Sent: Wednesday, May 19, 2010 9:11 AM
&g
serv.com]
Sent: Wednesday, May 19, 2010 9:39 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] msbuild command line parameters
I've successfully used DefineConstants before. I used it to provide external
paths to locations I was harvesting. Of course, a repo
sider the environment before printing this e-mail
> -Original Message-
> From: Kurt Jensen [mailto:kurt.jen...@ophir-spiricon.com]
> Sent: Wednesday, May 19, 2010 7:30 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] msbuild com
ginal Message-
From: Kurt Jensen
Sent: Tuesday, May 18, 2010 2:41 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: RE: [WiX-users] msbuild command line parameters
I'll try. It is being built under VS2008 and TFS2008.
-Original Message-
From: Castro,
I'll try. It is being built under VS2008 and TFS2008.
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Tuesday, May 18, 2010 2:25 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] msbuild command
lto:kurt.jen...@ophir-spiricon.com]
> Sent: Tuesday, May 18, 2010 1:08 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] msbuild command line parameters
>
> Good idea but still not appearing in the build log.
>
> Any more ideas out there?
>
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Good idea but still not appearing in the build log.
Any more ideas out there?
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Monday, May 17, 2010 10:14 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] msbuild command line
ge-
From: Kurt Jensen [mailto:kurt.jen...@ophir-spiricon.com]
Sent: Monday, May 17, 2010 3:48 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] msbuild command line parameters
The PropertyGroup code is as follows:
bin\$(Configuration)\
obj\$(Configu
-Original Message-
From: Kurt Jensen [mailto:kurt.jen...@ophir-spiricon.com]
Sent: Monday, May 17, 2010 3:05 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] msbuild command line parameters
I'm trying to build my wixproj in msbuild. The solution
ConfigurationToBuild is "Release|An
e-
> From: Kurt Jensen [mailto:kurt.jen...@ophir-spiricon.com]
> Sent: Monday, May 17, 2010 2:05 PM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] msbuild command line parameters
>
> I'm trying to build my wixproj in msbuild. The solution
> ConfigurationToBui
I'm trying to build my wixproj in msbuild. The solution
ConfigurationToBuild is "Release|Any CPU". Inside of my configuration
the wixproj is built as "Release|x86".
In my wixproj I have a 'Release|x86' PropertyGroup that includes
. But none of the DefineConstants are being included
on the co
Good day to Wix community!
Is it possible to pass a parameter inside MSBuild generated bootstrapper?
I would like to pass a 'SA' password for the SQL Server Express setup along
with some other setup options.
According to a Package.xml file taken from SQL Server express bootstrapper
(C:\Pro
.
Subject: RE: [WiX-users] Msbuild/Votive Change WIX Path
You'll need to set both WixTasksPath and WixTargetsPath. They need to point to
the WixTasks.dll and Wix.targets file respectively.
Try:
/p:WixTasksPath=C:\wix3.0\bin\WixTasks.dll
/p:WixTargetsPath=C:\wix3.0\bin\Wix.targets
Normally these
or Windows Installer XML toolset.
Subject: Re: [WiX-users] Msbuild/Votive Change WIX Path
Hi
Sorry I need more help, please
I have an old and working installation with Wix 3.0. this works fine For new
installation projects now I use wix 3.5. If I try to build the old installation
project with m
guration=Release /t:rebuild
>
> Does not work.
>
> Any ideas?
>
> regards
> Robert
>
> -Ursprüngliche Nachricht-
> Von: Blair [mailto:os...@live.com]
> Gesendet: Mittwoch, 20. Jänner 2010 19:20
> An: 'General discussion for Windows Installer XML toolse
/t:rebuild
Does not work.
Any ideas?
regards
Robert
-Ursprüngliche Nachricht-
Von: Blair [mailto:os...@live.com]
Gesendet: Mittwoch, 20. Jänner 2010 19:20
An: 'General discussion for Windows Installer XML toolset.'
Betreff: Re: [WiX-users] Msbuild/Votive Change WIX Path
So
On 1/20/2010 1:19 PM, Blair wrote:
> Wix.targets uses the $(WixTasksPath) property,
See "Integrating WiX Projects Into Daily Builds" in WiX.chm for more info.
--
sig://boB
http://joyofsetup.com/
--
Throughout its 18-ye
: 'General discussion for Windows Installer XML toolset.'
Subject: RE: [WiX-users] Msbuild/Votive Change WIX Path
Votive (and the related WiX support for MSBuild) use the $(WIX) property
(which is normally set from the %WIX% environment variable).
-Original Message-
From:
@lists.sourceforge.net
Subject: [WiX-users] Msbuild/Votive Change WIX Path
Hi
How can I change the path of the WIX-Tools for Msbuild/Votive?
I have old installer projects (build with Wix 3.0) an I want to build
them, but if I try to build them msbuild use the new wix version.
regards
Robert
Hi
How can I change the path of the WIX-Tools for Msbuild/Votive?
I have old installer projects (build with Wix 3.0) an I want to build
them, but if I try to build them msbuild use the new wix version.
regards
Robert
-
30 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] MSBuild inside Wix development
Thanks. I'm sure it's in there somewhere, but MSBuild is not Visual Studio -
it's part of .Net (oddly IMHO). And if you search the index for MSBuild
you'll fi
rom: [EMAIL PROTECTED] [
> [EMAIL PROTECTED] On Behalf Of Chris Mumford [
> [EMAIL PROTECTED]
> Sent: Wednesday, June 18, 2008 9:52 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] MSBuild inside Wix development
>
> Well in part
: Wednesday, June 18, 2008 9:52 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] MSBuild inside Wix development
Well in part because these have evolved for a while and I've been using them
for at least three years - possibly before wix.targets became part of
gt; [EMAIL PROTECTED]
> Sent: Tuesday, June 17, 2008 8:04 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] MSBuild inside Wix development
>
> You don't want to call MSBuild *from* WiX. Instead you want to mave MSBuild
> call WiX. Attac
junho de 2008 00:05
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] MSBuild inside Wix development
You don't want to call MSBuild *from* WiX. Instead you want to mave MSBuild
call WiX. Attached is my MSBuild project file that calls candle.exe and
light.exe to
May be I am not getting.. Please guide me .. Given below is my situation..
- We have completed MSBuild based batch files to complete the number of
task to build developer assemblies, Build biztalk assemblies, Deploying
Biztalk assemblies inside the Biztalk server.
- Now we want to pac
neral discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] MSBuild inside Wix development
You don't want to call MSBuild *from* WiX. Instead you want to mave MSBuild
call WiX. Attached is my MSBuild project file that calls candle.exe and
light.exe to build an MSI file.
Y
You don't want to call MSBuild *from* WiX. Instead you want to mave MSBuild
call WiX. Attached is my MSBuild project file that calls candle.exe and
light.exe to build an MSI file.
You can see that I have the path to the WiX bin folder hard-coded (and my
machine is x64). So as an improvement you co
Hi,
I am new to Wix and MSBuild area. I have one fundamental quention.
I completed all the building of my application in MSBuild. Now I am writing
Wix construction. I was under impressing we can call the MSBuild project
inside Wix.
I am trying examples for this. But unfortunately I didn't get th
line in
the project file to
Neil
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Richardson
Sent: May-08-08 3:07 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] MSBuild -- candle/light path
HI there,
Forgive my MSBuild-noobness...
HI there,
Forgive my MSBuild-noobness...
When using MSBuild, it looks like the WiX executables (candle/light)
are located via a registry key. Can this be overridden?
Thanks,
-kevin
-
This SF.net email is sponsored by t
im
Subject: Re: [WiX-users] MSBuild with multiple localizations
One question, Tim...
It looks like you only fire candle once.
In the element, there is a Language attribute. Currently for
that attribute, I use $(env.langid), set in the batch file before
running candle for each language.
What
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kevin
Richardson
Sent: 07 May 2008 05:24
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] MSBuild with multiple localizations
Greetings,
Does anyone have an example of building multi-language WiX installers
with MSBuild? I've looked a
Greetings,
Does anyone have an example of building multi-language WiX installers
with MSBuild? I've looked at the single-language examples, but what
I'd like to do is have a .wixproj that builds an installer in 10+
languages.
My current process uses the WiX tools manually through batch file
t;
> On 9/25/07, Peter Wone <[EMAIL PROTECTED]> wrote:
>>
>> Any Visual Studio Solution file (*.sln) is in the right format.
>>
>>
>>
>> *From:* [EMAIL PROTECTED] [mailto:
>> [EMAIL PROTECTED] *On Behalf Of *Jessi Darling
>> *Sent:* Wednesday, 26
AIL PROTECTED]> wrote:
>
> Any Visual Studio Solution file (*.sln) is in the right format.
>
>
>
> *From:* [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Jessi Darling
> *Sent:* Wednesday, 26 September 2007 7:11 AM
> *To:* wix-users
> *Subject:* [WiX-
Have a look at this MSDN article:
http://msdn.microsoft.com/msdnmag/issues/07/03/WixTricks/
//a
On 9/25/07, Jessi Darling <[EMAIL PROTECTED]> wrote:
>
> Could someone please show me an MSBuild file example?
>
> --
> Jessica Darling
> ---
Could someone please show me an MSBuild file example?
--
Jessica Darling
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct
My error. I only configured the cultures setting in debug version. On build
server it builds release versions.
Problem solved
/Baldie
Baldie wrote:
>
> Did this issue get resolved? I have the same problem.
>
> I have a solution containing a Wix project. The wixproj file contains the
> en-US e
Did this issue get resolved? I have the same problem.
I have a solution containing a Wix project. The wixproj file contains the
en-US element. When i build this solution from Visual
Studio the -cutures:en-US switch gets passed to light correctly.
But when i try to build the solution on our build
Martin Evans wrote:
Yes, the .wixproj has en-US;en-GB
Is it worth posting my .wixproj file?
Maybe. I don't know why it wouldn't get passed to the command line.
--
sig://boB
http://joyofsetup.com/
-
This SF.net email is s
Yes, the .wixproj has en-US;en-GB
Is it worth posting my .wixproj file?
Bob Arnson <[EMAIL PROTECTED]>
24/07/2007 03:28
To
Martin Evans <[EMAIL PROTECTED]>
cc
wix-users@lists.sourceforge.net
Subject
Re: [WiX-users] MSBuild / localisation variable problem - culture
information n
Martin Evans wrote:
It would appear that the Light.exe cmd run by MSBuild does not contain
the -culture information because when I do the following it is OK.
Light.exe -ext "WixUIExtension.dll" -cultures:en-us -out "c:\Web UI
Setup.msi" C:\...\WebUiSetup.wixobj
Stabbing in the dark a bit
setting/editing
in the wix.targets file?
Martin Evans
Development Manager
Achiever Business Solutions
Mailto:[EMAIL PROTECTED]
Bob Arnson <[EMAIL PROTECTED]>
23/07/2007 14:54
To
Martin Evans <[EMAIL PROTECTED]>
cc
wix-users@lists.sourceforge.net
Subject
Re: [WiX-users] MSBuil
Martin Evans wrote:
C:\delivery\Dev\wix_public\src\ext\uiextension\wixlib\BrowseDlg.wxs(18):
error LGHT0102: The localization variable !(loc.WixUIOK) is unknown.
Please ensure the variable is defined.
Is that the only error you get? Does it build correctly on your local
machine outside VS?
This is my first post, so please bear with me.
I'm using weekly build 3.0.3113.0 but have tried the previous two/three
weekly builds.
When I build locally in Visual Studio all is well, but when we do a
continuous integration build using MS build on our buildserver I get the
following:
C:\deli
I have a .wproj project where there is a variable Configuration defined. So
I can conditionally build the .msi I would like to "pass" this
$(Configuration) to Wix (I am assuming that I would pass it to candle). Does
anyone know how I can change the .wproj file so that this Configuration
variable (w
I'm not really sure what the answer is to this, but to me it doesn't seem
the ideal approach. The point of the bootstrapper is to make it easier for
the user to install without having to figure out the exact dependencies and
so on. For unattended installs, the admin usually knows the dependencies,
Hi,
I use msbuild to generate standard bootstrapper (using GenerateBootstrapper
element) which produces setup.exe and several depended folders with selected
prereqesites.
My question is whether I can run the setup.exe in a "quiet" mode with no UI
interaction (license dialogs displayed by the s
IL PROTECTED]; 'Francis Kam'; 'Michael F. Collins,
> III'
> Cc: 'WiX-users'
> Subject: RE: [WiX-users] MSBuild Tasks
>
> Hi Rob,
>
> I made lots of changes to the MSBuild wix.targets a while back to fix a
> few bugs, but got stymied by the (to me
chael Luke you saved me lots of time!
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Michael Luke
> Sent: 12 May 2006 09:22
> To: [EMAIL PROTECTED]; 'Francis Kam'; 'Michael F. Collins,
> III'
> Cc: '
Neil Sleightholm wrote:
> I have raised a request, id 1544363.
>
Thanks.
> Could you let me know where the "patch and assignment agreement" is?
>
That was "(patch) and (assignment agreement)." See
http://blogs.msdn.com/robmen/archive/2004/04/14/112970.aspx for details.
--
sig://boB
http://
I have raised a request, id 1544363.
Could you let me know where the "patch and assignment agreement" is?
Neil
-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 17 August 2006 16:22
To: Neil Sleightholm
Cc: WiX-users
Subject: Re: [WiX-users] MSBuild T
Neil Sleightholm wrote:
> Could the v3 version be back ported to the v2 version so it is included
> in future releases?
>
Probably. If you enter a feature request at
http://sourceforge.net/tracker/?group_id=105970&atid=642717, it'll get
into the queue. It'll happen faster if you submit a patch
PROTECTED] On Behalf Of Neil
Sleightholm
Sent: 15 August 2006 06:58
To: WiX-users
Subject: Re: [WiX-users] MSBuild Tasks
I'll take a look but v3 is not stable enough for my builds. Do you know
if the v3 wix.targets would work with v2?
Neil
-Original Message-
From: Bob Arnson [mailto:[E
I'll take a look but v3 is not stable enough for my builds. Do you know
if the v3 wix.targets would work with v2?
Neil
-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 14 August 2006 23:13
To: Neil Sleightholm
Cc: WiX-users; [EMAIL PROTECTED]
Subject: Re: [WiX-
Neil Sleightholm wrote:
> Would it be possible for this version of wix.targets to be adopted by
> the team as the one that is currently distributed doesn't work with
> multiple wsx files?
>
You might want to take a look at the WiX tasks/targets in WiX v3; it's
been enhanced beyond what's in v2.
eeds to be
released.
-Original Message-
From: Derek Cicerone [mailto:[EMAIL PROTECTED]
Sent: 14 August 2006 21:48
To: 'Simon Burgess'; 'Neil Sleightholm'; 'WiX-users'
Cc: [EMAIL PROTECTED]
Subject: RE: [WiX-users] MSBuild Tasks
That kind of incremental support
'WiX-users'
Cc: [EMAIL PROTECTED]
Subject: Re: [WiX-users] MSBuild Tasks
This email touches on a problem I'm having. I'm also using MSBuild (via
TeamBuild) to talk to WiX to generate msi's. There is mention here of
support for incremental build as '(a task wi
uild perhaps or
otherwise)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Neil
Sleightholm
Sent: 14 August 2006 20:41
To: WiX-users
Cc: [EMAIL PROTECTED]
Subject: Re: [WiX-users] MSBuild Tasks
Would it be possible for this version of wix.targets to be adopted by
th
D] On Behalf Of Michael Luke
Sent: 12 May 2006 09:22
To: [EMAIL PROTECTED]; 'Francis Kam'; 'Michael F. Collins,
III'
Cc: 'WiX-users'
Subject: RE: [WiX-users] MSBuild Tasks
Hi Rob,
I made lots of changes to the MSBuild wix.targets a while back to fix a
few bugs, but go
100 matches
Mail list logo
