Sure thing. I’ll probably dig through the burn source code.
Thanks Phill.
> On Jul 15, 2015, at 1:58 PM, Phill Hogland wrote:
>
> I cannot speak to not using Burn, but in the last link that you originally
> posted, the last post indicates that the information was posted earlier in
> that thread,
I cannot speak to not using Burn, but in the last link that you originally
posted, the last post indicates that the information was posted earlier in
that thread, so I would guess that there is an MSI property that controls
it. WiX is open source so it should be in the code for research. I also
e
What if ‘not’ using a Burn bundle?
> On Jul 15, 2015, at 6:14 AM, Phill Hogland wrote:
>
> Using a Burn bundle set Bundle/@DisableModify="button"
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-an-ARP-button-for-Uninstall-Ch
Using a Burn bundle set Bundle/@DisableModify="button"
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-an-ARP-button-for-Uninstall-Change-vs-Uninstall-Change-tp7600885p7600886.html
Sent from the wix-users mailing list archive at Nabble.com
I've been trying to google around for how to create a single
"Uninstall/Change" button in the windows ARP for my installer, and
I've run into a number of forum posts that don't seem to answer the
problem:
http://installjournal.blogspot.com/2012/12/combining-uninstall-change-on-same.html
http://st
I prefer to us a RegistryValue as the KeyPath.
The name and value could be anything, such as the path to the folder or the
app's version, but the registry value gets used as the KeyPath for the
component, allowing the GUID to be auto generated. I would rather take the
hit, I
I am required to create an installer that will install the files on Program
Files or Program Files(x86) depending upon the OS. Upon installation, I
want to create another folder inside CommonAppDataFolder and write the
newly created folder in environement path.
I have attached the code below:
htt
Thanks for the fantastic detailed clarification on this issue! I will endeavour
to use the melt approach outlined in Bob's post.
-Nick
--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET i
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Nick Ramirez [mailto:nickra...@hotmail.com]
Sent: Thursday, January 8, 2015 8:02 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Creating pat
Hi,
Currently i am trying to create slide show animation during installation. I
have some following queries.
How can i add a billboard control to the standard ProgressDlg ? Where
exactly in the element i have to do this? Which exact element i
have to use?
I have read some forum that "to alter t
Sounds like undocumented functionality of Melt. I don't see anything about
using it that way in the WiX.chm.
Also, binder variable don't solve the problem of binding the source files
into the XML file. They only give you a way to list a bunch of paths to
probe. So they don't replace the functiona
Subject: Re: [WiX-users] Creating patches using wixout (-bf flag deprecated)
Bind paths vs. Visual Studio project references (e.g.
$(var.MyProject.TargetDir))...the latter doesn't require passing custom
parameters to light. Why make the specifying of a source file more arcane with
a bind
Bind paths vs. Visual Studio project references (e.g.
$(var.MyProject.TargetDir))...the latter doesn't require passing custom
parameters to light. Why make the specifying of a source file more arcane
with a bind paths binder variable? Especially when the use case is a patch
file in the unseen futur
t: Thursday, January 8, 2015 11:50 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Creating patches using wixout (-bf flag deprecated)
You need to start using the bindpath variables in your wxs sources. Melt will
take care of pointing the wixpdb
@lists.sourceforge.net
Subject: Re: [WiX-users] Creating patches using wixout (-bf flag deprecated)
Ouch. So now you have to keep your old and new source files on hand. Would be
nice to keep the bind-files option or work it into the wixpdb. Also, not being
able to bind the files into the wixout or
-users] Creating patches using wixout (-bf flag deprecated)
Ouch. So now you have to keep your old and new source files on hand. Would be
nice to keep the bind-files option or work it into the wixpdb. Also, not being
able to bind the files into the wixout or wixpdb means that if you move the
wixout
Ouch. So now you have to keep your old and new source files on hand. Would be
nice to keep the bind-files option or work it into the wixpdb. Also, not
being able to bind the files into the wixout or wixpdb means that if you
move the wixout/wixpdb and then try to run Pyro against it, all the paths
a
@lists.sourceforge.net
Subject: [WiX-users] Creating patches using wixout (-bf flag deprecated)
Hi All,
I am using light.exe to create .wixout files with the -bf flag, I now get a
warning saying that this flag is deprecated. I can't find information on why.
I'm using .wixout files with bundle binary data
Hi All,
I am using light.exe to create .wixout files with the -bf flag, I now get a
warning saying that this flag is deprecated. I can't find information on why.
I'm using .wixout files with bundle binary data to create patches (as described
in the Wix 3.6 book) and am now wondering if this is
The terms upgrade, patch and component have specific meanings in
Windows Installer, so some of your meaning may not be obvious.
However:
A patch is a patch, an msp file, so just go search for -creating
patches with wix-
By definition a patch contains only the changes to the files that need
updati
Hello,
As part of our requirement, we need to create an upgrade patch on top of the
main package, the upgrade patch should only installed the components which is
part of the patch and similarly on uninstall should uninstall the component and
replace it with the old component.
Any help on how t
Here's an update. It seems that when building the patch it only includes my
added sqlscript if I also change some files. Is that expected behaviour?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-a-patch-tp7597504p7597524.html
Sent from t
Hi
I'm running som tests on my msi and some simulated patches before releasing
my RTM package and have some problems/questions
1. When creating my patch 1.0.1.0 I do that with my Msi 1.0.0.0 as baseline.
But when creating 1.0.2.0 patch, what baseline msi should I use?
2. It seems that an updated
Hi,
I created a web setup using Wix Designer add on for visual studio and
the msi works fine except it allows installation only for admin. I was able
to install using msiexec from elevated command prompt. I created an exe
with setupbld.exe, but the created exe is of the same size as msi which
Hi All,
Do we create an MSI package without installing WIX toolset in target
machine?
Any help on this?
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databas
s I'm missing something, the whole MS
> Isolated storage system, although often encouraged, seems very
> difficult to work with especially during an uninstall or if wishing to
> migrate settings during an upgrade.
>
> Cheers,
> Paul
>
>
> -Original Message-
> F
aged, seems very
> difficult to work with especially during an uninstall or if wishing
> to migrate settings during an upgrade.
>
> Cheers,
> Paul
>
>
> -Original Message-
> From: David Watson [mailto:dwat...@sdl.com]
> Sent: 31 March 2014 17:13
> To: General di
ng an uninstall or if wishing to migrate settings during an upgrade.
Cheers,
Paul
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: 31 March 2014 17:13
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Creating Isolated Storage for main assembly duri
The reason I coded that tidbit this morning was to lead u to ensure
that the XML File you're reading, and the ISOTest.exe your using are
both in the same Directory, or storage area what ever you want to call
it. From the sound of this post and your answer to me. you may be
suffering from
t may this binding that's going a bit weird?
-Original Message-
From: paul.chor...@stfc.ac.uk [mailto:paul.chor...@stfc.ac.uk]
Sent: 31 March 2014 16:06
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Creating Isolated Storage for main assembly during
it's install
the DEBUG & RELEASE builds in VS that affects
this which I cannot find or understand.
Cheers,
Paul
-Original Message-
From: Carter Young [mailto:ecyo...@grandecom.net]
Sent: 31 March 2014 14:48
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Creating Isolated Storage for main
Change:
try
...
isoFileStream = new
IsolatedStorageFileStream("RemotingConfig.xml", FileMode.Create, store);
to:
try
...
isoFileStream = new
IsolatedStorageFileStream(String.Concat(Application.StartupPath,"RemotingConfig.xml",
FileMode.C
Hello,
I have a simple VS2010 C# project that consists of:-
ISOTest.exe - The only assembly representing the main application which is
installed in the ProgramFiles folder using WIX. This has a public class:-
public class ExposeIsolatedStorage
{
public static IsolatedStorageFi
Hi All,
I had appended this query in another topic, so reposting the same under
different heading.
I have this requirement in which i want to create directory under
C:\Programdata same as what the user specified in the UI dialogue .I am
trying to do that using . Below is the code:
Thanks Bob, It is working. I have another one doubt, how can we get the
downloading package name. I should show the downloading msi package name in
UI. I have created a custom BA. In which Event i will get the acquiring
package name?
Thanks,
Saravana
--
View this message in context:
http://wi
On 17-Feb-14 07:17, Periyasamy Chinnu wrote:
> I am using Wix 3.6. I would like to create web installer using wix burn. I
> saw the link for adding executable files in remote payload element and it
> works.
> Like this how can i specify for msi?.
RemotePayload is just to avoid having the packages d
Hi,
I am using Wix 3.6. I would like to create web installer using wix burn. I
saw the link for adding executable files in remote payload element and it
works.
Like this how can i specify for msi?. I need to create a web installer that
downloads msi and cab files from server and installs it in cli
What is "standalonesimulator.exe"’s file id?
Blair
From: Suvrajyoti Panda
Sent: Tuesday, January 14, 2014 11:27 PM
To: General discussion for Windows Installer XML toolset.
Hi All,
I am creating an wix installer. I want to create a registry entry whose
path is not unde
Hi All,
I am creating an wix installer. I want to create a registry entry whose
path is not under the directory structure created in the WIX file. Below
is what i intend to do:
Hi Nicolas,
I just got it reviewed and as of now it does not cause much of a bother
to me at this point of time. Thanks for the reply.
Thanks,
SuvraJyoti
On 16-12-2013 21:12, Nicolás Alvarez wrote:
> Does he extra slash cause you actual trouble? Does it bother you enough to
> justify a custom ac
Does he extra slash cause you actual trouble? Does it bother you enough to
justify a custom action?
El lunes, 16 de diciembre de 2013, Suvrajyoti Panda escribió:
> Thanks for the solution Blair. Would try this.
>
> Regards,
> SuvraJyoti
> On 15-12-2013 16:24, Blair Murri wrote:
> > Only with a cu
Thanks for the solution Blair. Would try this.
Regards,
SuvraJyoti
On 15-12-2013 16:24, Blair Murri wrote:
> Only with a custom action
>
>
>
>
>
>
> -Blair
>
>
>
>
>
> From: Suvrajyoti Panda
> Sent: Thursday, December 12, 2013 9:51 PM
> To: General discussion for Windows Installer XML
Only with a custom action
-Blair
From: Suvrajyoti Panda
Sent: Thursday, December 12, 2013 9:51 PM
To: General discussion for Windows Installer XML toolset.
Hi All,
May be this is a trivial question to ask, but below is what i want to
achieve:
I am creating registry en
On 12/13/13, 3:46 PM, Markus Ewald wrote:
> On 12/14/2013 12:18 AM, Edwin Castro wrote:
>> On 12/13/13, 3:07 PM, Markus Ewald wrote:
>>> warning LGHT1076 : ICE69: Mismatched component reference. Entry
>>> 'ApplicationStartMenuShortcut' of the Shortcut table belongs to
>>> component '
On 12/14/2013 12:18 AM, Edwin Castro wrote:
> On 12/13/13, 3:07 PM, Markus Ewald wrote:
>> warning LGHT1076 : ICE69: Mismatched component reference. Entry
>> 'ApplicationStartMenuShortcut' of the Shortcut table belongs to
>> component 'ApplicationShortcut'. However, the formatted str
On 12/13/13, 3:07 PM, Markus Ewald wrote:
> warning LGHT1076 : ICE69: Mismatched component reference. Entry
> 'ApplicationStartMenuShortcut' of the Shortcut table belongs to
> component 'ApplicationShortcut'. However, the formatted string in
> column 'Target' references file 'myappl
On 12/13/2013 11:21 PM, Bevan Weiss wrote:
> I would suggest using two separate components for it.
> Each Shortcut is really a file..
> Then each would get its own HKCU registry entry.
>
> Is your installer PerUser or PerMachine?
> The HKCU entry might not be so appropriate for a PerMachine install
I would suggest using two separate components for it.
Each Shortcut is really a file..
Then each would get its own HKCU registry entry.
Is your installer PerUser or PerMachine?
The HKCU entry might not be so appropriate for a PerMachine install.
Bevan
2013/12/13 Markus Ewald :
> Hi!
>
> I'm try
On 12/13/2013 5:30 PM, Nicolás Alvarez wrote:
> Is this an upgrade? Are you testing it with an older version of the
> product (containing a single shortcut) already installed?
No, it's a completely new installer and I do not plan to bother with
upgrade installs at all.
Regards,
Markus Ewald
-
2013/12/13 Markus Ewald :
> Hi!
>
> I'm trying to add a second start menu shortcut to my installer, but it
> just doesn't add the second shortcut. I can't find any message
> indicating why in msiexec's install log either.
>
>
>
>
>
> Id="ApplicationStartMenuShortcu
Hi!
I'm trying to add a second start menu shortcut to my installer, but it
just doesn't add the second shortcut. I can't find any message
indicating why in msiexec's install log either.
I've tried creating two components (
Hi All,
May be this is a trivial question to ask, but below is what i want to
achieve:
I am creating registry entries as below in WIX source file:
2:21 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Creating Wix Pure patch with Melt.exe and Pyro.exe fails
I have been testing the 2 patching methods for WiX:
Using Patch Creation Properties
Using Purely WiX
I have created basic samples for both and got both of them working okay so
2:21 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Creating Wix Pure patch with Melt.exe and Pyro.exe fails
I have been testing the 2 patching methods for WiX:
Using Patch Creation Properties
Using Purely WiX
I have created basic samples for both and got both of them working okay so
the file versioning rules on MSDN.
> > http://msdn.microsoft.com/library/windows/desktop/aa368599.aspx
> >
> > > -Original Message-
> > > From: Phil Wilson [mailto:phildgwil...@gmail.com]
> > > Sent: Wednesday, November 13, 2013 10:39 AM
> > &
gt; > From: Phil Wilson [mailto:phildgwil...@gmail.com]
> > Sent: Wednesday, November 13, 2013 10:39 AM
> > To: General discussion about the WiX toolset.
> > Subject: Re: [WiX-users] Creating multiple Minor Updates
> >
> > You need to increment the file versions for patc
Tim,
Thanks for getting this recognized as a bug :)
-Original Message-
From: TimM [mailto:timmay...@smarttech.com]
Sent: November-14-13 9:19 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Creating Wix Pure patch with Melt.exe and Pyro.exe
fails
Thanks Blair, I have
)
-Original Message-
From: TimM [mailto:timmay...@smarttech.com]
Sent: November-13-13 5:05 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Creating Wix Pure patch with Melt.exe and Pyro.exe
fails
Here is part of my build log and all are referring to binary and merge Id
Thanks Blair, I have created bug #4187.
I have added, to the bug, the dropbox link to the zipped up product files
that can be used to reproduce the issue as well. So hopefully a solution to
this issue can be found or at least maybe let me know what I could possibly
be doing that may be causing thi
That looks like a melt bug to me. Please file it and if you can please link a
copy of the/a repro.
Blair
> Date: Wed, 13 Nov 2013 14:05:11 -0800
> From: timmay...@smarttech.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Creating Wix Pure patch with Melt.exe
bout the WiX toolset.
> Subject: Re: [WiX-users] Creating multiple Minor Updates
>
> You need to increment the file versions for patched files, basically because
> updates are based on them.
>
> http://msdn.microsoft.com/en-us/library/aa367835(v=vs.85).aspx
>
> Something l
Here is part of my build log and all are referring to binary and merge Id's
that are listed in fragment files and referencing the path that our build
machine created for the build:
D:\BuildAgent72\work\9f69624fb270635f\BoardSW\install\win\SMART Product
Drivers
\Core_x86PNPDrivers.wxs(158) : error
I have been testing the 2 patching methods for WiX:
Using Patch Creation Properties
Using Purely WiX
I have created basic samples for both and got both of them working okay so I
am now try a real install upgrade patch.
So I get the .msi and .wixpdb files for say version 1.0 and for version 1.1
S
: Wednesday, November 13, 2013 10:53
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Creating multiple Minor Updates
Is there any way to unsubscribe from this mailing list?
-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: Wednesday, November 13
Is there any way to unsubscribe from this mailing list?
-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: Wednesday, November 13, 2013 10:39 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Creating multiple Minor Updates
You need to
tems and all changes in the self-same fragments are included
> >> while all changes in unreferenced fragments are ignored. That is not the
> >> expected use case for most products.
> >>
> >> -Blair
> >>
> >>> Date: Tue, 12 Nov 2013 18:42:03
u
>> reference items and all changes in the self-same fragments are included
>> while all changes in unreferenced fragments are ignored. That is not the
>> expected use case for most products.
>>
>> -Blair
>>
>>> Date: Tue, 12 Nov 2013 18:42:03 -0800
>
most products.
>
> -Blair
>
> > Date: Tue, 12 Nov 2013 18:42:03 -0800
> > From: horanag...@gmail.com
> > To: wix-users@lists.sourceforge.net
> > Subject: Re: [WiX-users] Creating multiple Minor Updates
> >
> > I am more confused now.
> Subject: Re: [WiX-users] Creating multiple Minor Updates
>
> I am more confused now.
>
> Do we have to mention changed binaries (.dlls, .ocxs, .exes) in component
> reference...
>
> Please someone help here, how to do perfect patch??
>
> I foll
I am more confused now.
Do we have to mention changed binaries (.dlls, .ocxs, .exes) in component
reference...
Please someone help here, how to do perfect patch??
I followed steps in Wix 3.5 tutorial, without luck..
Any help would be appreciated.
--
View this message in con
lset.
Subject: Re: [WiX-users] Creating Cumulative patches with Patch Creation
Properties
I also have a post with a rough outline of a project to make a patch using
admin installs at:
http://borgsdemons.com/blog/2013/10/14/wixproj-skeleton-to-make-a-wix-way-patch/
I'll try and update i
.
Subject: Re: [WiX-users] Creating Cumulative patches with Patch Creation
Properties
I haven’t used PCP/PatchWiz in years because if all the problems PatchWiz
caused in the build farms I have to use with most of the projects I have worked
on.
In this blog post, Peter describes a way to use “Pure
I haven’t used PCP/PatchWiz in years because if all the problems PatchWiz
caused in the build farms I have to use with most of the projects I have worked
on.
In this blog post, Peter describes a way to use “Pure WiX” using an MSI not
created by WiX:
http://petermarcu.blogspot.com/2008/05/wix-
It is expected that for most products you never need more than one PatchFamily
and you NEVER need to reference anything inside of it (which will then update
all changes (and nothing except the changes) between the two MSIs).
Blair
From: TimM
Sent: Tuesday, October 29, 2013 11:
I am currently testing the creation of WiX patches using Patch Creation
Properties. Now I am trying this over Pure WiX patches because the versions
that we will initially be patching have already been released and when they
were built they were NOT built to generate the .wixpdb files. So we have to
Joe, we are just looking at patches and I have a question about this method
if you don't mind?
I am just testing out with using the sample 'Using Pure WiX' example and I
am looking at the PatchFamily element and noticed that you have to add a
reference to a component in your main install project.
o...@jackhenry.com
www.jackhenry.com
-Original Message-
From: MrWiX [mailto:philipp.ew...@asamnet.de]
Sent: Monday, August 12, 2013 12:11 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Creating a system restore point using burn
According to the log file
[2013-08-12T17:22:2
According to the log file
[2013-08-12T17:22:27]i360: Creating a system restore point.
[2013-08-12T17:22:27]i362: System restore disabled, system restore point not
created.
the bootstrapper is already trying to create a system restore point. Does it
fail only because of some system settings, or co
What would be really handy is a ba/ux with a feature tree selection driving
multiple msi packages. This would need to be in addition to WixStdBA, but
"getting it right" and doing it in a reusable way isn't a trivial task.
Handling upgrades would be especially tricky as a bundle can't currently
Microsoft Office 2007 has a single entry in ARP that can be used to
modify/remove the installed products. I wonder if they are using Burn to do
that.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-separate-entries-in-Add-Remove-for-each-M
Are you installing some sort of suite of different products? Maybe the
Visible flag on the MsiPackage element will get you closer to what you want.
Or there might be a way to build a custom BA that would present a screen to
remove particular products.
--
View this message in context:
http://wi
t automatically uninstalled if the Bundle is uninstalled)?
>
> -Original Message-
> From: nianderneves [mailto:niander.ne...@gmail.com]
> Sent: June 27, 2013 15:10
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Creating separate entries in Add/Remove for
...@gmail.com]
Sent: June 27, 2013 15:10
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Creating separate entries in Add/Remove for each MSI in a
bundle
Hello,
Can I generate separate entries in Add/Remove for each MSI that my bundle
installs?
The bundle just put a reference for him in
Hello,
Can I generate separate entries in Add/Remove for each MSI that my bundle
installs?
The bundle just put a reference for him in Add/Remove.
I want that my bundle put a a reference for him in Add/Remove and also a
reference for each MSI that the bundle instaled. The bundle would give the
opt
That's great. Thank you for your help - much appreciated.
Suzy
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: 26 June 2013 19:59
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating setup.exe from WiX msi file
Two
ssage-
From: Suzy Smith [mailto:su...@aspensoftware.co.uk]
Sent: June-26-13 3:39 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating setup.exe from WiX msi file
Thanks Wes. I've found that property. Any idea how I can stop the
bootstrapper displayin
n...@dynagen.ca]
Sent: 26 June 2013 18:46
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating setup.exe from WiX msi file
Recommended approach here is to use bundle to show GUI and have MSI behind the
scenes controlled with properties. But depending on th
Message-
From: Suzy Smith [mailto:su...@aspensoftware.co.uk]
Sent: June-26-13 2:43 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Creating setup.exe from WiX msi file
Hello
I've created a VS2012 project with WiX which produces an msi file. It has a
user interface and works a
Hello
I've created a VS2012 project with WiX which produces an msi file. It has a
user interface and works as I'd like it to. Now I've been asked to create a
setup.exe so I added a Bootstrapper project and reference my msi file in the
bundle - see below
Hi,
I am creating a .msi for my application and met some problems with it.
1. I have one solution with 6 projects. After I installed the application,
there will be one .exe file, 60 .dll files and some .config files in my
installed folder. Is there any easier way to add these 60 .dlls? Do I nee
t is what you are doing it may be worth a go.
>
> -Original Message-
> From: Joe Flynn [mailto:roo...@gmail.com]
> Sent: 22 May 2013 20:01
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Creating multiple Minor Updates
>
> Hi All,
>
> I have create
ject: [WiX-users] Creating multiple Minor Updates
Hi All,
I have created a product MSI which is versioned 6.100.0 . I have then
successfully created a minor update which installs as 6.100.1. Below is the
patch.wxs file I use to accomplish this:
http://schemas.microso
Ah gotcha. Thanks :)
/Thomas
> -Original Message-
> From: Phil Wilson [mailto:phil.wil...@mvps.org]
> Sent: 22. maj 2013 19:57
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: Re: [WiX-users] Creating patches
>
> If you want to s
Hi All,
I have created a product MSI which is versioned 6.100.0 . I have then
successfully created a minor update which installs as 6.100.1. Below is the
patch.wxs file I use to accomplish this:
http://schemas.microsoft.com/wix/2006/wi";>
http://www.mycompany.com"
tCode, MsiRunningElevated etc.
Phil
-Original Message-
From: Thomas Due [mailto:t...@scanvaegt.dk]
Sent: Tuesday, May 21, 2013 11:36 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating patches
Would you mind expanding on that? Because I don't know wha
Would you mind expanding on that? Because I don't know what you mean...
/Thomas
> -Original Message-
> From: Phil Wilson [mailto:phil.wil...@mvps.org]
> Sent: 21. maj 2013 18:58
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: Re
I think a check for the PATCH property is more typical.
Phil
-Original Message-
From: Thomas Due [mailto:t...@scanvaegt.dk]
Sent: Tuesday, May 21, 2013 6:09 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating patches
I was reviewing the
age-
> From: MrWiX [mailto:philipp.ew...@asamnet.de]
> Sent: 21. maj 2013 10:32
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Creating patches
>
> Identical file versions are definitely not the problem. (I just ran a test
> with
> WiX 3.7 and it work ju
o: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Creating patches
>
> Identical file versions are definitely not the problem. (I just ran a test
> with
> WiX 3.7 and it work just fine. Only got a warning that the patch contains to
> files.) It looks like your wixpdb
Identical file versions are definitely not the problem. (I just ran a test
with WiX 3.7 and it work just fine. Only got a warning that the patch
contains to files.)
It looks like your wixpdb files differ in more just the version number. Even
the referenced files are the same, the internal structur
1 - 100 of 625 matches
Mail list logo