unsubscribe
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover
Hägerlund [mailto:matti.hagerl...@gmail.com]
Sent: Wednesday, November 18, 2009 7:17 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] unsubscribe
Eh?
/M4tti
2009/11/18 Robert O'Brien robert.obr...@microsoft.com:
unsubscribe
.
Subject: Re: [WiX-users] unsubscribe
The footer of each message sent has a link to
https://lists.sourceforge.net/lists/listinfo/wix-users which has the
unsubscribe method.
Chris
On Wed, Nov 18, 2009 at 10:22 AM, Robert O'Brien
robert.obr...@microsoft.com wrote:
Been trying various supported
My wix-users@lists.sourceforge.net subscription settings configured with Mail
Delivery = disabled . . . and yet I'm still getting list emails. Am I missing
something about how to make this subscription setting take effect?
in the wix 3.5 release work is a file | new | project | wix | patch project
template going to eventually get included?
--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event
requirement in order to compile will really have no
effect, e.g. it shouldn't matter whether or not at install time the default web
site is configured with a port 80 binding.
From: Thomas S. Trias [mailto:tomtr...@artizan.com]
Sent: Wednesday, April 08, 2009 6:33 PM
To: Robert O'Brien
Cc
for more details:
http://blogs.msdn.com/mpoulson/archive/2006/03/06/544893.aspx
Neil
-Original Message-
From: Robert O'Brien [mailto:robert.obr...@microsoft.com]
Sent: 09 April 2009 16:51
To: 'tomtr...@artizan.com'
Cc: Dmitry Frenkel; 'General discussion for Windows Installer XML toolset
sql:Database ConfirmOverwrite=no expected
cause the db not being created if it already exists?
No. It removes the prompt when an overwrite will occur.
-Original Message-
From: Robert O'Brien [mailto:robert.obr...@microsoft.com]
Sent: Monday, February 09, 2009 08:39
To: 'General discussion
?
iis:WebSite Id=DefaultWebSite SiteId=0 Description=Default Web
Site/iis:WebSite
-Original Message-
From: Robert O'Brien [mailto:robert.obr...@microsoft.com]
Sent: Wednesday, April 08, 2009 4:19 PM
To: 'tomtr...@artizan.com'; 'General discussion for Windows Installer XML
toolset
Message
Subject: Re: [WiX-users] is it a bug that iis:WebSite doesn't locate
presence ofexisting website using just the Name attribute value
versusportsettings?
From: Robert O'Brien robert.obr...@microsoft.com
To: 'General discussion for Windows Installer XML toolset
We have a service deliverable msi where optionally have some w08/iis70 Default
Web Site vdir settings we want to apply and some Site1 Web Site and Site2
Web Site settings we want to apply (see relevant excerpt below). We need to
allow for deployments where Site1 Web Site and Site2 Web Site
-be-changed-in-a-patch-or-transform.aspxfor
more information.
On Sun, Sep 14, 2008 at 1:28 PM, Robert O'Brien robert.obr...@microsoft.com
wrote:
Thanks that appears to be exactly what my issue was with my adminInstall
output. I used orca to reconfigure the feature level settings in my v1.0
action needs elevated privileges to apply changes to the machine.
Be great if you could open a documentation bug to suggest that this be more
specific.
-Original Message-
From: Robert O'Brien [mailto:robert.obr...@microsoft.com]
Sent: Friday, January 30, 2009 11:47
To: 'General discussion
Thanks for responses.
1. setting the SKIPCONFIGUREIIS property via an immediate CA (scheduled prior
to ConfigureIIs of course) to simply skip IIS configuration when the target
host already has the website installed would require us having some way to
determine if the target host already
the limitation but the code does expect
things to behave the way you list. If you think it should be different,
feel free to file a feature request with a clear statement of what you
see and what you would prefer.
Robert O'Brien wrote:
I agree getting the exec wrapped statements correct, required so we
is there a way to get a dll.config file deployed along side a gac destined
file, e.g. a File .../ entry with Assembly=.net defined?
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC
with Assembly=.net defined?
I don't believe there is any supported way, WiX or otherwise, to put a
config file in the GAC. I am curious why you would want to?
Neil
-Original Message-
From: Robert O'Brien [mailto:robert.obr...@microsoft.com]
Sent: 27 February 2009 17:15
To: General
can I expect that a ServiceControl Id=BtsSvc
Name=BTSSvc$BizTalkServerApplication Start=both Stop=both Wait=no /
entry without the Remove attribte specified just handles start/stop behavior of
an existing service and does not try and install and/or remove it?
what I wanted.
Michael
-Original Message-
From: Robert O'Brien [mailto:robert.obr...@microsoft.com]
Sent: Thursday, 12 February 2009 5:48 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] any insights as to why sql extension commands
containing
Any pointers on the syntax i should one use to enable deployment of a gac dll
required dll.config file, e.g. gac dll's that make use of the setting
designer/api runtime settings?
I tried the following two options and the first doesn't work because it seems
the file copy to the gac of the
And $Sdk1Gac14=3/Custom
From: Robert O'Brien
Sent: Thursday, February 19, 2009 9:13 AM
To: 'wix-users@lists.sourceforge.net'
Subject: any pointers on the syntax i should one use to enable deployment of a
gac dll required dll.config file, e.g. gac dll's that make use if setting
designer/api runtime
Any pointers on the syntax i should one use to enable deployment of a gac dll
required dll.config file, e.g. gac dll's that make use if setting designer/api
runtime settings?
I tried the following two options and the first, currently commented out,
doesn't work because it doesn't drop the file
any pointers on the syntax i should one use to enable deployment of a gac dll
required dll.config file, e.g. gac dll's that make use if setting designer/api
runtime settings?
I tried the following two options and the first, currently commented out,
doesn't work because it doesn't drop the file
Would Custom Action=ExecXmlFile be more relevant than Custom
Action=SchedXmlFile for ensuring my util:XmlFile settings get applied just
before my CAQuietExec deferred custom action that needs those settings in place?
From: Robert O'Brien
Sent: Friday, February 13, 2009 1:46 PM
To: 'General
i need util:XmlFile associated SchedXmlFile action to happen before a specific
CAQuietExec deferred custom action .
Would using the following sequence entry for SchedXmlFile be the correct /
supported way to make that happen?
Custom Action=SchedXmlFile Before=SetMyCaQeAction!Database1=2 And
Any insights as to why the following sql extensions commands that create a sql
login and db user setting work
Property Id=DATABASESHOST Value=localhost
sql:SqlDatabase Id=MasterDatabase Database=master Server=[DATABASESHOST]
/
sql:SqlDatabase Id=Database1 Database=MyDeliverableDatabase
pair ExecuteOnUninstall=yes
RollbackOnInstall=yes correct to control having the specific setting applied
during uninstalls and also during component install rollbacks?
From: Robert O'Brien
Sent: Wednesday, February 11, 2009 11:28 AM
To: General discussion for Windows Installer XML toolset.
Subject
pair ExecuteOnUninstall=yes
RollbackOnInstall=yes correct to control having the specific setting applied
during uninstalls and also during component install rollbacks?
From: Robert O'Brien
Sent: Wednesday, February 11, 2009 11:28 AM
To: General discussion for Windows Installer XML toolset.
Subject
is setting sql:Database ConfirmOverwrite=no expected cause the db not being
created if it already exists?
--
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax
is customaction impersonate attribute default when attribute is not specified
yes or no . . . the current chm details does not say which
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] does util:XmlFile or util:XmlConfig or util:???
have some way of just doing a token search and replace throughout an entire
file?
No.
-Original Message-
From: Robert O'Brien [mailto:robert.obr...@microsoft.com
I have a bindings.xml file that my wix component deploys that I then need to
roll through and just do a search and replace of all localhost hits before
this file gets processed by an After=InstallFiles custom action.
Does util:XmlFile or util:XmlConfig or util:??? have some way of just doing
a
Looking for some clarification on conditions to use for sequencing activities
to cover install | modify add feature | rollback | modify remove feature |
uninstall cases.
I usually end up having one type of custom actions that are feature or
component specific and intended to provision things
the Componentization during day to day development to try to do
more optimal minor upgrade or patching. Major upgrades are just easier
(although less optimal).
-Original Message-
From: Robert O'Brien [mailto:[EMAIL PROTECTED]
Sent: Friday, December 05, 2008 08:34
To: 'WiX-users'
Subject: Re: [WiX-users
could also use a CustomAction using the Error attribute and
you could sequence this after CostFinalize to achieve the same effect.
Robert O'Brien-2 wrote:
Is it expected that prerequisite condition statements support checking
feature state and action values in order to determine if prerequisite
Great news and congratulations on reaching this milestone.
A while back I posted some questions to the forum about how to structure an msi
to automatically set REINSTALL and REINSTALLMODE property settings to necessary
values for patch and minor upgrade processing. There were working
is it possible for Installed to be set during rollback processing, e.g.
rollback custom actions should always have at least a Not Installed not a
Installed entry in their sequence condition?
--
SF.Net email is Sponsored
Is it expected that prerequisite condition statements support checking feature
state and action values in order to determine if prerequisite should be checked
for, e.g. is the following valid given an msi that has a Feature named
Databases and a SQL08DIR property assignment using registry
is there a canned way for authoring a prerequisite that checks for the presence
of another msi installed product, e.g. w/o using registry or directory or file
searches?
-
This SF.Net email is sponsored by the Moblin Your
Any tips on why the following xmlfile machine.config install changes are not
working?
I'm using the following component entries:
util:XmlFile Id=AddBehaviorExtensionsEnableBizTalkHeaderInspector
File=[NetFramework20ConfigDir]machine.config
,
Microsoft.IT.RelationshipManagement.Services.WcfExtensions, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35/
]]/util:XmlConfig
-Original Message-
From: Robert O'Brien [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2008 11:39 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX
\.NETFramework
Name=InstallRoot
DirectorySearch Id=Nfx20X86InstallRootSearch Path=v2.0.50727
Depth=0 /
/RegistrySearch
/Property
-Original Message-
From: Robert O'Brien
Sent: Monday, December 01, 2008 4:17 PM
To: 'General discussion for Windows Installer XML toolset
XML
v3\bin\WixNetFxExtension.dll installed by the Wix3_x64.msi installer was built
with Target=x86 versus Target=x64?
-Original Message-
From: Rob Mensching
Sent: Monday, December 01, 2008 7:07 PM
To: General discussion for Windows Installer XML toolset.; Robert O'Brien
Subject: RE: [WiX
Root=HKLM Key=Software\Microsoft\.NETFramework Name=InstallRoot
DirectorySearch Id=Nfx20InstallRootSearch Path=v2.0.50727
Depth=0 /
/RegistrySearch
/Property
-Original Message-
From: Rob Mensching
Sent: Monday, December 01, 2008 7:29 PM
To: Robert O'Brien; General
Not sure I'm just using standard issue file | new | wix project template
generated wixproj to wrap build process with Build Configuration Platform=x64
enabled.
-Original Message-
From: Rob Mensching
Sent: Monday, December 01, 2008 7:40 PM
To: Robert O'Brien; General discussion
name. New names: InstallSqlData and UninstallSqlData.
-Original Message-
From: Robert O'Brien [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 20, 2008 12:29
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] what's the custom action name I use to sequence
Using the following vdir component setup
Component Id=Site1Vdir1 Guid=15280DB5-1879-4D3D-A559-566FCA21FB77
!--File Id=InstalledSite1Vdir1.txt Name=InstalledSite1Vdir1.txt
Source=Resources\InstalledComponent.txt KeyPath=yes /--
!-- if you introduce a shortcut then you need to use an HCKU
e.g. is using wixproj | properties | settings | suppress specific ice
validation = ICE38;ICE43;ICE57 considered acceptable?
-Original Message-
From: Robert O'Brien [mailto:[EMAIL PROTECTED]
Sent: Friday, November 21, 2008 3:37 PM
To: 'General discussion for Windows Installer XML toolset
ConfigureSql
On Wed, Nov 19, 2008 at 9:24 PM, Robert O'Brien [EMAIL PROTECTED]
wrote:
I have a custom action that I wanted to schedule to happen just before
CreateDatase processing occurs. I tried the following custom action
sequencing statement
Custom Action=QtExecCmdLineRun5 Before
using ADDLOCAL and friends. That
might work better...
-Original Message-
From: Robert O'Brien [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 19, 2008 14:05
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] correct way to enable commadn line support
to show up
in the tree or not.
-Original Message-
From: Robert O'Brien [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 20, 2008 14:36
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] correct way to enable commadn line support for
defining features
Up until a half hour ago when I started yanking no longer required feature
condition statements my WixUI_FeatureTree UI experience was displaying features
in the order that they were defined in the sources, e.g.
e.g. if this was the order I entered my features in my sources this was the
order
=[IISWEBSITE] Directory=MainWebDirectory AutoStart=yes
WebApplication=MainWebApplication
DirProperties=WebDirPropertiesAnonymous
iis:WebAddress Id=WebsiteWebAddressPort
Port=[IISPORT] /
/iis:WebSite
/Component
-Original Message-
From: Robert
I have the following logic in each of my feature/subfeature settings so that
from the command line users can easily define what features/subfeatures are
selected and unselected by default when they step into the interactive install
or run and unattended install.
When I run my msi in
:36 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] using a variable for Component Win64 attribute value
still generating generic warning not uniquely suppressible in wixproj | build |
suppress specific warnings field
Robert O'Brien wrote:
Any insights on how
If I use the following
Property Id=DATABASESHOSTNAME Value=[%ComputerName]
my log output shows something other than what I'd expect
Property(S): DATABASESHOSTNAME = [%ComputerName]
and my CreateDatabase call that uses the public property DATABASESHOSTNAME fails
If I use the following
Property
I have a custom action that I wanted to schedule to happen just before
CreateDatase processing occurs. I tried the following custom action
sequencing statement
Custom Action=QtExecCmdLineRun5 Before=CreateDatabaseNot
Installed/Custom
and when I compile I get the following error
Error 1
I looked under the current wix help file how to section and could only find
How To: NGen Managed Assemblies During Installation.
This appears to cover having wix generated msi's install/uninstall to
%systemroot%\assembly\gac_32 %systemroot%\assembly\gac_64 but does not appear
to have an
only finds the NativeImage element. Probably should tweak the
documentation to catch both.
-Original Message-
From: Robert O'Brien [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 18, 2008 03:58
To: 'General discussion for Windows Installer XML toolset.'; '[EMAIL PROTECTED]'
Subject: Re
Background
--
A while ago I raised an issue to do with a warning being generated when using a
variable for the Component Win64 attribute value. Below you'll see the an
excerpt of the logic I'm using so that in the case of all managed code
deliverables I can create one set of wix
the How To: Generate a GUID document (excerpt below) suggests that wix
supports compiling with PUT-GUID-HERE tokens vs actual Guid values or where
allowed * token autogenerated Guid values defined...but the PUT-GUID-HERE
tokens case isn't working with the latest install
All examples in the How
what is the recommended way for setting the AppPool associated with a new
iis:WebSite? Lots of samples on this for the case of an iis:WebVirtualDir but
nothing that made sense in the case of an iis:WebSite where creating a child
iis:WebApplication doesn't make sense given that's typically a
There are many msi based setups I've used in the past, office and vstudio for
example, where a custom command line is provided that allows you to run an
interactive .msi session and at the end of it capture to a .mst all the
settings you chose but not actually do the install.
Does current wix
will persist the property value or not? If not Why? What is other way of
implementation, beacuse i dont want to pass property value while Uninstallation.
Please anyone help me
Thanks Regards,
Chandrashekar vuppala
M-9908298419
From: Robert O'Brien [mailto
a new element. Or you can switch to XmlConfig and insert a
document fragment.
-Original Message-
From: Robert O'Brien [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 23, 2008 13:14
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] how does one get
I believe the default behavior of the UIRef Id=WixUI_Mondo / and UIRef
Id=WixUI_FeatureTree / maintenance mode UI experience is that it provides
users the option of only selecting specific features currently installed that
they would like removed.
-Original Message-
From: Sandeep
In my v1.0 release I had shortcut settings in multiple components using start |
programs | My Service Deliverable menu folder.In my v1.1 release I
changed the wix sources to use start | programs | My Service Deliverable
v1.1. When I run a v1.0 to v1.1 msp patch or msi upgrade I end up
Background:
-
I have a wix souce file with the following XmlFile entry
util:XmlFile Id=Service1IServiceGatewayEndpointIdentity
File=[#NsService.exe.config]
fyi - in my wix sources I'm able to successfully set/use util:xmlfile
elementpath values with attribute search qualifiers using the following
escaping syntax.
util:XmlFile ... ElementPath='//[EMAIL PROTECTED]third\]'/
You can use alternatively:
util:XmlFile ... ElementPath=//[EMAIL
it to show
up...its probably because when I was testing this I was still setting
REINSTALL=ALL and REINSTALLMODE=vomus on the command line.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert O'Brien
Sent: Wednesday, September 17, 2008 6:08 PM
To: 'wix
PROTECTED] On Behalf Of Robert O'Brien
Sent: Thursday, September 18, 2008 1:15 AM
To: 'wix-users@lists.sourceforge.net'
Subject: Re: [WiX-users] create setup.exe
fyi - msi minor upgrade detection using QFEUpgrade=1 property setting condition
is no longer working for me, i.e. qfeupgrade property
I have a msp patch and msi minor pgrade processing result where a specific
app.config file setting which has underwent some miner content changes in the
v1.1 release is not getting updated.
If I diff my v1.0 target adminInstall and my v1.1 update adminInstall used to
by the old msimsp patch
Here is what I'm now using to accomplish this w/o needing a setup.exe wrapper,
e.g. you can just double click the msp and/or msi. Initial knowledge share
for the double click msp property settings solution this came from John
Nannenga.
!-- for msp small update or minor upgrade processing
That's was it. I had had one test build of my patch where it tested it doing
a v1.0 to v1.1 minor upgrade where the v1.1 wix had introduced a ServiceControl
entry. I used hyper-v snapshot to roll back to prior that msp patch minor
upgrade test pass and removed the v1.1 wix that had
the util:XmlFile applied settings. I haven't figured out yet
how to have the remove process reapply the util:XmlFile customizations to the
reverted version of that file. Any suggestions are welcome.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert
1. when I run a v1.0 to v1.1 msp patch upgrade [ or a v1.0 to v1.1 msi
upgrade ] am I expected to include the additional public property settings that
were needed/used when I ran the original v1.0 deployment, e.g. INSTALLDIR,
DATABASESHOSTNAME, DATABASESDOMAINLOGINGROUPNAME, etc.?
2. is
Got answers to these. Would be interested if anyone already has a command line
utility wrapping MsiRemovePatches api that allows cmd.exe scripted removal of
patches.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert O'Brien
Sent: Monday, September
: Saturday, September 13, 2008 9:40 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] using torch.exe -ax to enable use of admin install msi
target and update input parameter values
Robert O'Brien wrote:
Any insights on what could be in my pretty typical wix3
Arnson
Sent: Saturday, September 13, 2008 9:22 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] is there a way to get current wix vs08 project
extensions to output a patch msp?
Robert O'Brien wrote:
Question - if the only thing different in the light command
q1 - In the new wix3 way patch msp generation xml is there a way to specify the
PatchFamily element to cover get the msp patch generated to cover changes to
all components from v1.0 to v1.1 versus having what appears to be the need to
specify every component explicitly as the patch help
\$(Configuration) where it always used
to land
Robert O'Brien wrote:
The syntax of the command is incorrect.
That message is coming from cmd.exe; you need to put it in a target instead.
--
sig://boB
http://joyofsetup.com
Installer XML toolset.
Subject: Re: [WiX-users] getting working v1.0 - v1.0 minor update using msp
msi solutions pulled together
Robert O'Brien wrote:
q1 - should I expect that minor upgrade using msp or msi can shuffle a new
dll into place that may be loaded in an active window service process w
\$(Configuration)\en-us versus bin\$(Configuration) where it always used
to land
You should be able to add it anywhere inside the postbuild Target. What error
did you get?
Neil
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Robert O'Brien [EMAIL
PROTECTED]
Sent
The blog
http://blogs.msdn.com/pmarcu/archive/2008/05/30/Patching-something-you-didnt-build-with-WiX-using-WiX-.aspx
outlines using torch.exe -ax switch to enable use of admin install msi target
and update input parameter values.
When I try and do that using the torch command syntax:
] On Behalf Of Robert O'Brien [EMAIL
PROTECTED]
Sent: Thursday, September 11, 2008 7:43 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] what setting causes current wix build output to land
in bin\$(Configuration)\en-us versus bin\$(Configuration) where it always
Does inclusion of msi minor upgrade wix sources in v1.1 msi block the ability
to also generate patch msp minor upgrade msp wix sources?
For example does having the following product.wxs sources prevent me from also
being able to generate a v1.0 - v1.1 patch msp minor upgrade msp wix sources?
:[EMAIL PROTECTED] On Behalf Of Robert O'Brien
Sent: Thursday, September 11, 2008 2:20 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] does inclusion of msi minor upgrade wix sources in v1.1
msi block the ability to also generate v1.0 - v1.1 patch msp minor upgrade
\$(Configuration)\en-us versus bin\$(Configuration) where it always used
to land
Robert O'Brien wrote:
If I clear my wixProject | properties | build | cultures to build field and
rebuild I'm still getting output in the bin\$(Configuration)\en-us folder.
Is there a way to restore build
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Robert
O'Brien
Sent: 09 September 2008 19:20
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] does running upgrade msi or patch msistill
require additional command line switches?
Awesome thanks...so
Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert O'Brien
Sent: Thursday, September 11, 2008 1:33 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] what setting causes current wix build output to land
in bin\$(Configuration)\en-us
\$(Configuration)\wixLocalizationCultureAttribValue.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert O'Brien
Sent: Thursday, September 11, 2008 1:43 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] what setting causes
to your targets that work
with the output file locations.
Neil
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert O'Brien
Sent: Thursday, September 11, 2008 1:43 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users
, 2008 10:45 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] is there a way to get current wix vs08 project
extensions to output a patch msp?
Robert O'Brien wrote:
is there a recommended approach to getting current wix vs08 project
extensions to output a patch
Thanks for all the responses to my recent questions associated with getting
working v1.0 - v1.0 minor update using msp msi solutions pulled together.
At this point I believe I have what should be working sources and build output
to carry out a minor upgrade using both the msp msi approaches.
variable that's autogenerated during the
build is $(var.Platform).
-Jason-
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert O'Brien
Sent: Monday, September 08, 2008 7:35 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX
for Windows Installer XML toolset.
Subject: Re: [WiX-users] does running upgrade msi or patch msi still require
additional command line switches?
Bob Arnson wrote:
Robert O'Brien wrote:
q2 - do the same REINSTALLMODE switch settings apply when trying to
use a patch to carry out a minor or major upgrade
When I use the current wix project templates by default it creates projects
with Debug|x86 and Release|x86 configurations.
I'm interpreting the bug closure details below to suggest that I no longer need
to use Package InstallerVersion=200 Compressed=yes
Platform=$(var.TargetPlatform) / to set
what setting causes current wix build output to land in
bin\$(Configuration)\en-us versus bin\$(Configuration) where it always used to
land?
I have an existing solution deliverable containing a wix project created
initially using 4004. After migrating the file to contain the wixproj file
Sent: Friday, September 05, 2008 10:45 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] does running upgrade msi or patch msi still require
additional command line switches?
Robert O'Brien wrote:
Q1 - does running upgrade msi or patch msi still require
Robert O'Brien wrote:
what setting causes current wix build output to land in
bin\$(Configuration)\en-us versus bin\$(Configuration) where it always used
to land?
The Cultures setting. Every culture results in a culture-specific output
in the specified subdirectory.
--
sig://boB
http
1 - 100 of 167 matches
Mail list logo
