Murray,
Try writing the properties into registry values at install and then using the
Registry Search to read the values back into properties at the start of an
upgrade
Michael
-Original Message-
From: Murray Hipper [mailto:mhip...@snowdengroup.com]
Sent: Tuesday, 5 May 2009 3:17 PM
T
Murray
I know there is some stuff if you search through the history of this mailing
list. I don't know of any tutorials or other info, but that doesn't mean there
isn't any.
First what runs in an upgrade is really going to depend on if you are doing an
MSI Major Upgrade or Minor Upgrade. If
Hi All,
I am discovering the Upgrade process of MSI and how WiX handles it
thanks to the fantastic article at
http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-par
t-8-major-upgrade.aspx and I noticed that it has the MigrateFeatures
flag which is fantastic. Another thing which I
> -Ursprüngliche Nachricht-
> Von: Bob Arnson [mailto:b...@joyofsetup.com]
> Gesendet: Dienstag, 5. Mai 2009 02:59
> An: General discussion for Windows Installer XML toolset.
> Betreff: Re: [WiX-users] CopyFile: SourceProperty vs. SourceDirectory
>
> Reuss, Matthias wrote:
> > How do t
Hi Guys,
I wanted to ask the community for any best practices or methods used
with the upgrading of SQL Databases through WIX. The install step is
fine and pretty straight forward, the upgrade process is messy and I am
unsure what scripts will run and when. I did a quick search but wasn't
able to
Thank you, all, for the help. At this point I think I'm going to abandon WiX
and bite the bullet and just rebuild my VS .Net 2005 dev environment. It's not
my goal to fix the problems that exist within the Crystal merge module or
wrestle WiX into submission and force it to deal with the mess.
Found a workaround (and I came up with some sort of explanation for it).
Rule: If you use WIXPDB files when you call TORCH, you should always pass "-sf"
to PYRO.
Reason:
In order to generate the .wixpdb files you will pass to torch you must run the
binder in light.exe. The binder at that point
Hey Anthony,
There is no association with the VS packager and WiX. WiX is fully Windows
Installer compliant which is why you are seeing these issues. It is not that
WiX can't "handle" the MSM, it is that it would be doing so without giving
you, the developer, valid information for your product. Th
Anthony F wrote:
> I'll be the first to admit that I'm by no means an expert in the art of
> creating install packages, but if VS can handle the messed up msm, shouldn't
> wix be able to as well? I thought (I may be WAY wrong on this) that the VS
> packager was based on wix?
>
It is not bas
Reuss, Matthias wrote:
> How do the attributes SourceProperty and SourceDirectory differ?
>
They both map to MoveFile.SourceFolder. SourceDirectory also creates a
reference to the corresponding Directory Id. The MoveFiles action relies
on directory properties being created to support both app
David Bartmess wrote:
> That answers my question... Thanks. I can setup a custom action to check the
> allowed features that runs before the feature screen, I presume, and disable
> the features not allowed.
>
You get the same effect using feature conditions.
--
sig://boB
http://joyofsetu
I'm getting an error PYRO0130 in the table MsiAssemblyName which makes no sense
to me, especially since the wixmst file entry for that doesn't seem to match
the error message (at least to my mind). Why would modifying a field on a row
(when the field is not part of the primary key) generate this
I am very surprised that if I set my new dialog after ProgressDlg, then it
works.
Is there any potential problem if I run it like this?
--
View this message in context:
http://n2.nabble.com/How-do-I-modify-ProgressDlg-in-Wix-3-tp2788460p2789990.html
Sent from the wix-users mailing list archive
Yes, I did that.
Tom Kazimiers wrote:
>
> xubutian schrieb:
>> I copied and renamed ProgressDlg.wxs to MyProgressDlg.wxs, renamed dialog
>> to
>> MyProgressDlg.
>>
>> I also referenced new dialog in MyWixUI_Mondo.wxs:
>>
>> and in MyProgressDlg.wxs
>>
>>
>>
>>
>> I removed "back" and "next"
I have a hidden "skip" push button in ProgressDlg. When one of my differed
custom action begins to run, I hope to hide "cancel" button and show this
"skip" button. How do I do this?
And is it possible to enable/disable this new button from my custom action?
Thanks!
--
View this message in conte
xubutian schrieb:
> I copied and renamed ProgressDlg.wxs to MyProgressDlg.wxs, renamed dialog to
> MyProgressDlg.
>
> I also referenced new dialog in MyWixUI_Mondo.wxs:
>
> and in MyProgressDlg.wxs
>
>
>
>
> I removed "back" and "next" buttons from new dialog, but the result was not
> I expecte
Yes, and it spits out many, many errors including the "must contain
MSIPublishAssemblies and MSUUnpublishAssemblies" errors that I'm getting with
Wix. The problem here is that it works perfectly well when creating installers
in Visual Studio. I'll be the first to admit that I'm by no means a
Have you opened the Crystal Reports merge module in Orca and run a
Tools | Validation?
Wendell
On Mon, May 4, 2009 at 2:21 PM, Anthony F wrote:
>
> I've made some progress, but still get errors from light.
>
>
>
> The wxs file looks like this:
>
>
>
> Manufacturer='Microsoft Corporation'>
>
Hey Anthony,
The ICE39 (http://msdn.microsoft.com/en-us/library/aa368962(VS.85).aspx)
reads the summary stream; remove the Package/@Compressed='yes' to get rid of
that message. As for the ICE83, I would look at the documentation (
http://msdn.microsoft.com/en-us/library/aa369038(VS.85).aspx). It a
I've made some progress, but still get errors from light.
The wxs file looks like this:
I added the the 3
Hey Anthony,
Have you looked at the help documentation? There is a sample on how to do
that in there.
Brian Rogers
"Intelligence removes complexity." - Me
http://icumove.spaces.live.com
On Mon, May 4, 2009 at 1:37 PM, Anthony F wrote:
>
> I've been banging my head for the last few hours trying
What are the errors?
Can you email your wxs file and .cmd file for building and I'll take a look?
Thanks!
Wendell
On Mon, May 4, 2009 at 1:37 PM, Anthony F wrote:
>
> I've been banging my head for the last few hours trying to create a
> super-simple installer (my first) with wix. All I want
I've been banging my head for the last few hours trying to create a
super-simple installer (my first) with wix. All I want is an installer that
includes a single merge module... and that's it. No options, no gui, no
additional files. Just the merge module. I figured it would be a pretty
si
Hi
Solved the problem. After the first error (0x80070013) it copied the stub
EXE and retained the read-only permission on the EXE I specified in my
-output switch. I still had my output EXE with the read-only permission in
my output directory when I reran the command after changing the permissions
I copied and renamed ProgressDlg.wxs to MyProgressDlg.wxs, renamed dialog to
MyProgressDlg.
I also referenced new dialog in MyWixUI_Mondo.wxs:
and in MyProgressDlg.wxs
I removed "back" and "next" buttons from new dialog, but the result was not
I expected. It sounds like the old ProgressDlg w
Well, I ended up finding a solution to this. The app is a .NET app, which means
that the assemblies are versioned in Major.Minor.Build.Revision format.
Due to the way the compiler generates the Revision number, it can actually
"downgrade" for a newer version, which seems to confuse Windows Insta
I am experiencing the exact same behaviour with one of our installation
packages. Like you, we only do major upgrades.
Out of 17 files, 4 are getting missed on a major upgrade. I'm not convinced
that it has anything to do with versions, as almost every DLL has a different
version in the newer v
Hi Ben,
Description of DrLocator table
(http://msdn.microsoft.com/en-us/library/aa368331.aspx) states that Path column
has type AnyPath
(http://msdn.microsoft.com/en-us/library/aa367562(VS.85).aspx). Description of
AnyPath mentions that path may contain *properties* enclosed in square brackets
Hi
I've been trying to build a bootstrapper using setupbld, but keep getting a
result of 0x80070005 with a message that just states "Failed to
CreateSetup". Initially I received 0x80070013, but that went away after
removing the read-only property from setup.exe stub. My command has the
following s
Bob Arnson wrote:
> Tom Kazimiers wrote:
>
>> my MSI installer is made with WiX 3 and I wonder if there is a
>> possibility to uninstall the current installation (if any) of the
>> product and then installing the new one?
>> I am asking since I don't want to do a major upgrade every time I do a
That answers my question... Thanks. I can setup a custom action to check the
allowed features that runs before the feature screen, I presume, and disable
the features not allowed.
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Saturday, May 02, 2009 12:33 PM
To
Thank you so much! That fixed the problem.
This e-mail list is great! It really helps "newbies" like me. I was
really frustrated when I left work Friday not getting my code to work.
Now I feel very happy thanks to you.
Thanks again,
Fredrik
-Original Message-
From: Bob Arnson [mailto:b..
Hello,
How do the attributes SourceProperty and SourceDirectory differ?
I expect the SourceProperty attribute to translate into the sourceFolder column
of the MoveFile table. It is described as a Property whose value resolves to
the full path of the source directory. So if I enter any Directory
Dear All,
I have modified the WixUI_INSTALLDIR set to add a condition:
I am creating a dialog named "InstallDirConditionDlg" which informs the user
that the install path contains SPACE, and that the program will not work if
so.
I want to modify the InstallDirDlg to show the dialog:
http:/
Hi,
The database credentials for creating my database are taken during installation
via a dialog box. Using the login, password and server name details entered by
the user, I create the database during installation, using SQL authentication.
But when I am uninstalling, the database does not drop
Thanks for the information!
It has been very helpful.
Luciana
--- On Sat, 25/4/09, Heath Stewart wrote:
From: Heath Stewart
Subject: Re: [WiX-users] Is it allowed to remove all files within a component
with a patch?
To: istoc_luci...@yahoo.com, "General discussion for Windows Installer XML
I found out what the problem was: I wasn't providing the correct .wixpdb of the
baseline version (the paths to the files were not correct, they were pointing
to the new versions instead of pointing to the old version, from the baseline).
It seems that was the reason I was having problems when tr
37 matches
Mail list logo
