in that circumstance?
-Original Message-
From: XorPtr [mailto:reaper4...@gmail.com]
Sent: Wednesday, December 09, 2009 1:55 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patching problems with alternate directories
When you refer to the currently installed location
What does the log say about the component statuses?
-Original Message-
From: XorPtr [mailto:reaper4...@gmail.com]
Sent: Thursday, December 10, 2009 6:27 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patching problems with alternate directories
Hey Blair-2, I'd
@lists.sourceforge.net
Subject: Re: [WiX-users] Patching problems with alternate directories
Hey Blair-2, I'd be happy to share a log of the installation but
unfortunately I'm doing this for a company and I'm not allowed to post the
information for a log. I've studied the logs myself during
...@gmail.com]
Sent: Thursday, December 10, 2009 12:00 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patching problems with alternate directories
All of the components are listed as:
Installed: Local; Request: Local; Action: Local.
Blair-2 wrote:
What does the log say about
: Thursday, December 10, 2009 6:27 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patching problems with alternate directories
Hey Blair-2, I'd be happy to share a log of the installation but
unfortunately I'm doing this for a company and I'm not allowed to post
the
information
during
patch/repair/uninstall.
Thanks,
Tom
-Original Message-
From: XorPtr [mailto:reaper4...@gmail.com]
Sent: Thursday, December 10, 2009 12:59 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patching problems with alternate directories
I definitely
...@gmail.com]
Sent: Thursday, December 10, 2009 3:50 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patching problems with alternate directories
Thanks for the tip Tom, I'm looking into at least one discrepency that I
saw
come up after the Orca/patch transform. I'm not sure
: Wednesday, December 02, 2009 1:12 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patching problems with alternate directories
I've been having an issue with my WiX patch which I haven't been able to
find
any information for. The company I work for wants to give users
Subject: Re: [WiX-users] Patching problems with alternate directories
When you refer to the currently installed location, are you referring to
the location that my product installs to by default or the location selected
by the user. If the latter, then the patch should be installing to that
location
, 2009 1:12 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patching problems with alternate directories
I've been having an issue with my WiX patch which I haven't been able to
find
any information for. The company I work for wants to give users the
freedom
to install our
I've been having an issue with my WiX patch which I haven't been able to find
any information for. The company I work for wants to give users the freedom
to install our product in a directory of their choice. We've given the
installer a default directory which can be changed at install time by
[mailto:reaper4...@gmail.com]
Sent: Wednesday, December 02, 2009 1:12 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patching problems with alternate directories
I've been having an issue with my WiX patch which I haven't been able to
find
any information for. The company I work
Any ideas? Anyone?
-- Yan
-Original Message-
From: Yan Sklyarenko [mailto:y...@sitecore.net]
Sent: Friday, November 20, 2009 11:59
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patching: weird numbers for Media.DiskId
andFile.Sequence
Hello WiX Community,
I have been
: Monday, November 23, 2009 1:29 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching: weird numbers for Media.DiskId
andFile.Sequence
Any ideas? Anyone?
-- Yan
-Original Message-
From: Yan Sklyarenko [mailto:y...@sitecore.net]
Sent: Friday, November 20
Hello WiX Community,
I have been analyzing the log file of my patch installation, and faced
with a weird numbers I don't know the origin of. Here's the snippet:
...
TRANSFORM: The minimum 'Media.DiskId' value inserted by a patch
transform is 100
TRANSFORM: The maximum 'Media.DiskId' value
Hello
How do i apply a patch to a product that does not support Repair (Repair
disabled when it was shipped)
Running the patch silently from the command line does not seems to work
because I have a type19 custom action that is conditioned as REINSTALL = ALL
Any ideas??
-
Andy
MSI
@lists.sourceforge.net
Subject: [WiX-users] Patching after disabling Repair
Hello
How do i apply a patch to a product that does not support Repair (Repair
disabled when it was shipped)
Running the patch silently from the command line does not seems to work
because I have a type19 custom action
discussion for Windows Installer XML toolset.'
Subject: RE: [WiX-users] Patching after disabling Repair
If you can bootstrap your patch, you might be able to set REINSTALL to the
list of installed features instead of ALL. Otherwise you may be forced to
use a Major Upgrade.
-Original Message
will be
evaluated AFTER you transform it.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Wednesday, October 21, 2009 12:10 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: RE: [WiX-users] Patching after disabling Repair
If you can bootstrap your patch
@lists.sourceforge.net
Subject: Re: [WiX-users] Patching after disabling Repair
OK. In that case using a custom action that sets the ARPNOREPAIR value to
0
before the launch conditions/ would do the trick??
Blair-2 wrote:
The thought that followed right after I pushed Send is that in your
patch
it should be 0
(values are opposite).
From: wix-users-boun...@lists.sourceforge.net
[mailto:wix-users-boun...@lists.sourceforge.net] On Behalf Of Vitaly
Dolya
Sent: Sunday, June 18, 2006 7:46 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users
passing to torch?
-Original Message-
From: Gremlin [mailto:postingpl...@gmail.com]
Sent: Wednesday, July 29, 2009 6:54 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patching MergeModules
Hi there,
How can I patch MergeModules with pyro when they are packed
@lists.sourceforge.net
Subject: Re: [WiX-users] Patching MergeModules
I call torch like this:
torch.exe -p -xi Baseline\App.wixpdb Hotfix\App.wixpdb -out Diff.wixmst
then I candlelight the Hotfix.wxs:
candle.exe Hotfix.wxs -out Hotfix.wixobj
light.exe Hotfix.wixobj -out Hotfix.wixmsp
then I execute pyro
Hi there,
How can I patch MergeModules with pyro when they are packed in an msi?
My problem:
I have an msi with an msm included and I create the patches with pyro.exe
The patching works when I have to create a patch witch new files that are
defined in the msi. As soon as I get a new msm which
Which files are you passing to torch?
-Original Message-
From: Gremlin [mailto:postingpl...@gmail.com]
Sent: Wednesday, July 29, 2009 6:54 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patching MergeModules
Hi there,
How can I patch MergeModules with pyro when
Bob,
More info:
1. auto-generate GUIDs
When using option -ag, I have to manaully change * to a real GUID.
2. PatchWizard in WiX 3.0
With different GUIDs of components between two distributions, I can still
create a patch and install it properly. The log file shows that file id is
used in file
shibo wrote:
1. auto-generate GUIDs
When using option -ag, I have to manaully change * to a real GUID.
Why?
Is my finding correct?
I don't know. I'd go by the doc.
--
sig://boB
http://joyofsetup.com/
--
Bob,
1. GUIDs
Sorry, it is my mistake. -ag works. I got error msgs (error LGHT0231)
earlier due to my folder structure, installation not default to
ProgramFilesFolder. Checked new MSI files, yes, they share the same GUIDs.
2. Patching
Just try to find inside details how the difference is
.msp' differs in size with the
certificate authored in the package
-Original Message-
From: Chris Bardon [mailto:cbar...@computer-talk.com]
Sent: Thursday, July 02, 2009 5:48 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching a product without
Hi,
I am trying to patch a file that has the name and source (but different
content). So, I recompile the product .wxs file (which didn't change
since only the file contents changed and the source and name didn't
change) then I run torch then pyro. However, when I run pyro I get a
warning
My goal for getting patching to work is to be able to deploy an application
that can be patched by a non-admin user, but I'm running into a problem. I've
created the patching sample in the documentation, and the patch works when it's
elevated, but whether or not it's signed, the patch is still
Chris,
Those elements appear to simply identify what certificate should be
given the green light for patching. I believe you still need to
digitally sign the resulting MSI using signtool.exe.
- Rafael
Chris Bardon wrote:
My goal for getting patching to work is to be able to deploy an
I did run signtool against the packages, with the command lines in the first
part of the post.
I also forgot to point out a couple of other changes to the demo code. I
changed the installer version to 300, and I set ALLUSERS to 1 to make sure that
I installed per-machine to start with.
]
-Original Message-
From: Rafael Rivera [mailto:raf...@withinwindows.com]
Sent: Thursday, July 02, 2009 3:17 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching a product without elevation
Chris,
Those elements appear to simply identify
.
From: Rafael Rivera [raf...@withinwindows.com]
Sent: Thursday, July 02, 2009 4:03 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching a product without elevation
MSI (c) (24:FC) [15:23:03:419]: Certificate of signed
Hi,
Sorry for taking long to replay.
As far as I am aware it is not possible to set the version of the DLL's when
compiling each page and user control into a separate assembly.
If this is possible can someone point me in the right direction on how to do
this? I have down some searching but no
Hi,
I've run the patch example successfully:
http://blogs.msdn.com/astebner/archive/2007/10/26/5700191.aspx
Based on that example, how to build patch for a multi-language msi. For
example, I have a msi which is able to install an application in either
English(en-us) or French(fr-fr). That
WiX patching does support adding new components, but those components have
to be added to features in your products as well. They should also be in new
Fragments.
But if those features are optional features, adding new components to
optional and possibly absent features will cause prompt for
Hi,
I have a problem with patching a web deploy MSI I have created with WiX,
where each page has its own DLL.
If there have been minor changes to the code behind such that the size of
the compiled DLL does not change between builds the DLL will not be marked
as modified in the diff file, and as
I am having a hard time determining the best way to handle patching v1.0
with v1.n. I have all my wxs files built for v1.0, and would like to move
forward with v1.n. I have read the WiX doco, which explains the process of
building a patch Using Purely WiX. This process seems to assume v1.n will
Sean Gainsford wrote:
If there have been minor changes to the code behind such that the size of
the compiled DLL does not change between builds the DLL will not be marked
as modified in the diff file, and as such does not get patched. I presume
this it due to neither the file size nor version
We have a hotfix installer that replaces the old dll with a new dll in Program
Files/GAC.
It opens a handle for the file being replaced. So while replacement, if we do
not close this handle, an error is coming up - Access Denied.
In some products of our team itself, we are not seeing this error
[mailto:magra...@microsoft.com]
Sent: Tuesday, April 07, 2009 2:03 AM
To: Windows Installer Support (MS Internal); General discussion for Windows
Installer XML toolset.; Windows Installer Xml Virtual Team
Cc: Sandeep Prabhu
Subject: [WiX-users] Patching Issue
We have a hotfix installer that replaces
Installer XML toolset.
Subject: Re: [WiX-users] Patching SQL Database with script
The SqlScript element (or SqlString if you just want to run a couple
strings).
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric
Latendresse
Sent: Monday, July 28
If this code is running in a custom action, it is impersonated or not?
Phil Wilson
-Original Message-
From: cemiles [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 26, 2008 9:10 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patching SQL Database with script
action, it is impersonated or not?
Phil Wilson
-Original Message-
From: cemiles [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 26, 2008 9:10 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patching SQL Database with script
Is there an answer
:
If this code is running in a custom action, it is impersonated or not?
Phil Wilson
-Original Message-
From: cemiles [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 26, 2008 9:10 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patching SQL Database with script
there you can figure out why things were skipped.
-Original Message-
From: cemiles [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 26, 2008 09:31
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patching SQL Database with script
It's not in a CA I authored
: [WiX-users] Patching SQL Database with script
It's not in a CA I authored, but in ExecuteSqlStrings I thought.
Here's what I'm working with. msi installs fine and does what i want,
then
the msp succeeds (even if i set the patch script's continueonerror=no).
that's the part that's
, 2008 10:09
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patching SQL Database with script
Ok, the best (or most promising) place where it might be griping is here...
MSI (s) (CC:28) [13:05:24:039]: Doing action: ConfigureSql
Action 13:05:24: ConfigureSql. Configuring SQL Server
, November 26, 2008 09:31
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patching SQL Database with script
It's not in a CA I authored, but in ExecuteSqlStrings I thought.
Here's what I'm working with. msi installs fine and does what i want,
then
the msp succeeds (even if i
-
From: Chad Miles [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 26, 2008 10:26
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patching SQL Database with script
Just now Rob, and it looks like a flip flop.
During Install:
MSI (s) (CC:18) [12:58:31:859]: Component
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent: Monday, July 28, 2008 10:39 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching SQL Database with script
The SqlScript element (or SqlString if you just want to run a couple
Victor V. Sergeev wrote:
Yes, I'm adding new elements to existing component.
You can't do that in a minor upgrade/patch; it violates component rules,
which state that components are immutable.
--
sig://boB
http://joyofsetup.com/
Victor V. Sergeev wrote:
I'm trying to create a patch using Pyro (Version 3.0.4513.0). In that
patch i need to execute addition sql on a SqlServer database
When i'm using sqlstring element all OK. But, when I'll try to use
sqlscript element my patch fail...
How are you
Victor V. Sergeev wrote:
I'm trying to create a patch using Pyro (Version 3.0.4513.0). In that
patch i need to execute addition sql on a SqlServer database
When i'm using sqlstring element all OK. But, when I'll try to use
sqlscript element my patch fail whith error in log:
Action start
Hi,
I'm trying to create a patch using Pyro (Version 3.0.4513.0). In that
patch i need to execute addition sql on a SqlServer database
When i'm using sqlstring element all OK. But, when I'll try to use
sqlscript element my patch fail whith error in log:
Action start 11:04:08: InstallSqlData.
Hi,
I have an installation that creates a User and assigns it to a WebAppPool.
The credentials of the User are obtained through a custom dialog. I then
went on to create an MSP for this installation that replaces some files.
Everything works fine but when uninstalling the patch, it seems that
Hi,
I have an installation that creates a User and assigns it to a WebAppPool.
The credentials of the User are obtained through a custom dialog. I then
went on to create an MSP for this installation that replaces some files.
Everything works fine but when uninstalling the patch, it seems that
.
-Original Message-
From: Shawn Dwyer [mailto:[EMAIL PROTECTED]
Sent: Monday, August 18, 2008 11:24 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching fails with 1627
Thanks for the feedback and the helpful links. I've read all of Heath's
blogs a few times
Shawn Dwyer wrote:
So for anyone else running into this issue, apparently one of the causes
could be too many characters in the Id field of the TargetImage element,
which has a max length of 13 characters. The same for the UpgradeImage
element.
Can you file a bug? It sounds like
discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching fails with 1627
Hi,
I'm running into what seems to be a common error on the mailing list,
but
none of the solutions so far have worked for me.
I have 3 basic test patches:
RTM: installs file1
Patch1: targets rtm
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Tony Juricic [EMAIL
PROTECTED]
Sent: Monday, August 18, 2008 8:19 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching fails with 1627
Don't patch the patch!
Always target:
a) only RTM
] [
[EMAIL PROTECTED] On Behalf Of Tony Juricic
[EMAIL PROTECTED]
Sent: Monday, August 18, 2008 8:19 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching fails with 1627
Don't patch the patch!
Always target:
a) only RTM
b) RTM + another (non-patched) full
Hi,
I'm running into what seems to be a common error on the mailing list, but
none of the solutions so far have worked for me.
I have 3 basic test patches:
RTM: installs file1
Patch1: targets rtm, updates launch condition of RTM
Patch2: targets Patch1, updates file1 and installs directory2\file2
for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching SQL Database with script
The SqlScript element (or SqlString if you just want to run a couple
strings).
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric
Latendresse
Sent: Monday, July
My initial installer creates the SQL database perfectly, but I want to
be able to include new SQL scripts to be run with my patches. Could
someone give me some insight on how to do this?
Eric
-
This SF.Net email
The SqlScript element (or SqlString if you just want to run a couple strings).
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Latendresse
Sent: Monday, July 28, 2008 14:59
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users
I'm using the Wix 3 patching system (vs the system requiring msimsp) and
running into an issue when I try to patch on a French-language Windows;
basically it just refuses, I get an error saying the patch is not valid (and
no log is created, if I'm logging). But I can use this VERY SAME PATCH to
Hello,
I am creating patches for my application using the WIX patch build system. I
have encountered (so far) 2 (two) big problems related to 'wix.section.xx'
in the Wix pdbs.
First problem was that my patch included many components which I have not
specified in my Patch.wxs file. Debugging pyro
: Thursday, December 20, 2007 5:37 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patching fails to find files in cab.
I have created a semi-broken patch that I cannot figure out how to
troubleshoot.
First the basic info:
Used Wix 3 and MSIMSP to create patches.
For my product, I
Cristian N. Baiu wrote:
Most probably I will not have to patch the files in those directories
because they are not binaries.
But just in case : could you please detail the problems I might have
if I patch those files ? (if I will ever get a request to patch them
it would be good for me to
Hello,
I have a product which I've already delivered. The RTM setup of this
product was built with WIX 3.0.3210.0 and contains some directories
which unfortunatelly have the ID longer than 72 characters (they came
from a MSM and because of the MSM's GUID suffix they got longer than
72 - WIX had
Cristian Baiu wrote:
Obivously, I will need to cut shorter this directory ids in order to
be able to build my upgrade setup. The question is : will this affect
the patch (I will have the same components in the RTM and upgrade
setups but with different parents in the Directory tables) ?
-
From: Bob Arnson [EMAIL PROTECTED]
To: Cristian Baiu [EMAIL PROTECTED]
Cc: wix-users@lists.sourceforge.net
Sent: Friday, December 21, 2007 9:26 PM
Subject: Re: [WiX-users] Patching and the new limitation of Directory to 72
characters
Cristian Baiu wrote:
Obivously, I will need to cut shorter
I have created a semi-broken patch that I cannot figure out how to
troubleshoot.
First the basic info:
Used Wix 3 and MSIMSP to create patches.
For my product, I have version 1, 1.1, 1.2
Version 1.1 adds existing components to an existing feature so I have the
same components under more than 1
Hello,
Using WiX 2.0, I'm trying to set up a patching scheme where if the user
has installed a 1.00 version of the product they can apply patches they
come out for that version. However, I'm missing something big because I
can only get a single patch to work and no subsequent patches as they
fail
] On Behalf Of John Robbins
Sent: Sunday, December 09, 2007 6:35 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patching Pain
Hello,
Using WiX 2.0, I'm trying to set up a patching scheme where if the user
has installed a 1.00 version of the product they can apply patches they
come out
I'm trying to test out patching based on the following instructions,
http://blogs.msdn.com/pmarcu/archive/2007/06/28/sample-patch.aspx
Are these steps accurate? I get the following error on the final step.
I tried the latest and greatest version and then I went back to
3.0.3106.0 the closest to
Please keep /wix-users/ on the thread.
Petrut Andrei wrote:
Hello. Sorry for bothering you again. I need one more little help with
my patch.
I created and I can run it, but when I run it, it asks me whether I
should remove files or not. I just want to install the modified files,
not to delete
Grant Wagner wrote:
Reciently, we have grown a need to starting patching our application
in production. Using the technique at
http://wix.sourceforge.net/manual-wix2/patch_building.htm seems to
produce nice results until we starting adding or removing files. At
which point it failes
. Is this what
you are currently doing?
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Tuesday, June 05, 2007 8:27 AM
To: Grant Wagner
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patching Wix generated msis
Grant Wagner wrote:
Reciently, we have grown
Subject: [WiX-users] Patching a mergemodule or forcing an install
Our application is dependent on some MS Merge-modules which we have in our
installer, they are added via the Merge and MergeRef tags. Problem is the
mergemodules have a condition VersionNT = 500 or Version9X, this is a problem
: 13 April 2007 14:19
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patching, patching, and more patching.
Hello,
From research I have done, it appears that this type of question has
been asked a few times before (so please hang in there)...but I am still
a little sketchy
Neil Sleightholm wrote:
I am not an expert on patching but I would like to mention that
normally MSI's only understand 3 part version numbers. So 2008.0.14.0
and 2008.0.14.30 are seen as the same version by windows installer.
Fair point. Also note that the first two fields are limited to
Nick Hennemann wrote:
And it appears that the minor upgrades (service packs) would be
approximately the same size as the original install?
Depends on the extent of the changes. Minor upgrade patches can also
take advantage of delta patching so how well they delta and compress
controls
Hello,
From research I have done, it appears that this type of question has
been asked a few times before (so please hang in there)...but I am still
a little sketchy on the details of how to accomplish it or maybe if I am
understanding the process correctly.
Here is what I would like to do:
Hello,
From research I have done, it appears that this type of question has been
asked a few times before (so please hang in there)…but I am still a little
sketchy on the details of how to accomplish it or maybe if I am
understanding the process correctly.
Here is what I would like to do:
Nick Hennemann wrote:
* Create the RTM version of my installer
* Be able to patch the RTM version with any patch that I create for it
* Also be able to patch the RTM version that has already been
patched with a previous (earlier) patch
The MSI patching model supports that
[mailto:[EMAIL PROTECTED]
Sent: Friday, April 13, 2007 12:38 PM
To: Nick Hennemann
Cc: [EMAIL PROTECTED]
Subject: Re: [WiX-users] Patching, patching, and more patching.
Nick Hennemann wrote:
* Create the RTM version of my installer
* Be able to patch the RTM version with any
PM
To: Huck, Jacob
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patching fails with 1627
Huck, Jacob wrote:
In case someone was looking at a similar issue: basically we
have multiple cab files in a debug install (to contain the pdbs, which
exceed 2GB in many cases
Huck, Jacob wrote:
I was positive the spirit of the msdn doc was saying it would work
with PatchWiz 2.0 /or greater//, /but apparently not. They said
they'd improve the error message (long term) and write up a kb (short
term).
Thanks for the follow-up! It almost makes sense, as PatchWiz 2.0
Huck, Jacob wrote:
In case someone was looking at a similar issue: basically we have
multiple cab files in a debug install (to contain the pdbs, which
exceed 2GB in many cases). When generating the patch, I was leaving
MediaDiskId blank, but in needed to be set to a value greater than the
in the msi's.
Thanks
-jh
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Huck,
Jacob
Sent: Sunday, February 25, 2007 11:03 PM
To: Bob Arnson; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patching fails with 1627
Sounded promising, but unless
Huck, Jacob wrote:
ERROR: Failed to execute a view
ERROR:The Last Error Received is: 1627
ERROR:The Last Error Received is: 1: 2259 2:
c:\temp\~pcw_tmp.tmp\3000.MSI 3: 4:
I've gotten that before when I was use a File/Sequence column of I4; by
default, Patchwiz supplies
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Sunday, February 25, 2007 1:38 PM
To: Huck, Jacob
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patching fails with 1627
Huck, Jacob wrote:
ERROR: Failed to execute a view
ERROR:The Last Error
I'm currently building two varieties of my install, release and debug,
using WiX 3.0. Right now I'm able to successfully create an MSP using
msimsp 4.0 for the release msi's only; when I try to generate a debug
MSP, I get the following error:
ERROR: Failed to execute a view
ERROR:
Hi all.
Is there a method to create a patch that is able to
update all stages of a given product?
Say I have a product A.B.0 containing a certain exe.
This exe is changed in each patch, i.e. in 0-1, 1-2
etc.
I want a patch that's able to upgrade A.B.2 as well
as A.B.4 to, say, A.B.7.
I wrote:
Hi all.
Is there a method to create a patch that is able to
update all stages of a given product?
Say I have a product A.B.0 containing a certain exe.
This exe is changed in each patch, i.e. in 0-1, 1-2
etc.
I want a patch that's able to upgrade A.B.2 as well
as A.B.4 to,
Hi all.
I am curently trying to create a working .msp with Wix v3
So far I followed the Wix v2 tutorial and created a .msp
that is supposed to replace in file 'a.txt' the contents
'old stuff' by 'new stuff'.
When I run
msiexec '/l*v' PatchLog.txt /p patch.msp REINSTALL=ALL REINSTALLMODE=omus
101 - 200 of 207 matches
Mail list logo
