I'm afraid I have only ever done this as a major upgrade, I don't think
it should matter.
But would I have to change the version number for the major upgrd? All we
have is a minor change to one of the assemblies and this assembly could be
used to host a strongly typed remoting object. if I
I'm trying to package a legacy program that registers some third-party
ocx and dlls. I see that the consensus is that I should be handling
this with a registry component. However, this application's
'installer' just copies stuff into a folder off the root of c:\ and
runs a 'register.bat'
May be I am not getting.. Please guide me .. Given below is my situation..
- We have completed MSBuild based batch files to complete the number of
task to build developer assemblies, Build biztalk assemblies, Deploying
Biztalk assemblies inside the Biztalk server.
- Now we want to
Thank you very much Chris, that helped a lot.
I have been successfully using MSBuild to build the installers, but your
solution is cleaner.
Best regards,
Mello
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Mumford
Sent: quarta-feira, 18 de
Thanks for the quick reply. This does exactly what I wanted. After testing it
out, I have another question. After the upgrade, the old settings file is still
there. How do I remove the folder and the settings file for the last version?
Also, is it possible to remove the settings folder in the
Hi,
I have stored in a property a path where I need to create a folder and
afterwards copy in it some files.
I've played a bit with the CreateFolder element, but I don't know how
to parse the information stored in my property to correctly create the
directory.
I've also tried to use the
Hi Bob,
Thank your for pointing this out and helping me to clarify things.
Cheers Volker
Bob Arnson wrote:
Volker Enderlein wrote:
this way). The installer is started without elevation and defaults to an
per-user installation. Later the user/admin can change the preselection
in the GUI to
Hi,
I am doing a major upgrade and the Start Menu/Programs/OldEntry
folder is not removed. I would like to keep the OldEntry, but now, both
OldEntry and NewEntry exist in the Programs folder. Any ideas as to why
is the delete shortcuts action inhibited?
Best regards,
Calin
PS.
The
I wasn't suggesting you had to do a major update only that that was all I had
done. Have you tried enabling the logs during the install to see what it says
when it tried to install the file?
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
Hi all,
If I set version number like this:
Product Name=XXX 7.5.6.001' Id='{BB52FB21-F007-40ef-A73E-6717AE770446}'
Language='1033' Codepage='1252' Version='*7.5.6.001*' Manufacturer='XXX,
Inc.'
UpgradeCode='ebb5dec0-edce-4531-9d2b-668c8a7e0ba7'
after installation process in support
You can't, assembly version numbers are stored as numbers by the OS, so leading
zeros are stripped.
Neil
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Maxim Vyazovsky
Sent: Wednesday, June 18, 2008 8:31 AM
To: wix-users@lists.sourceforge.net
Subject:
hm,
http://i.piccy.kiev.ua/i2/45/c7/aea71120584104c1c6b99d3ba93e.jpeg
what about this?
On Wed, Jun 18, 2008 at 7:01 PM, Neil Enns [EMAIL PROTECTED] wrote:
You can't, assembly version numbers are stored as numbers by the OS, so
leading zeros are stripped.
Neil
-Original Message-
No idea how they did that. The second one isn't even a valid Windows file
version number. It must be a text string that comes from somewhere else,
although the Windows Installer property reference doesn't list any properties
for the version number.
Neil
-Original Message-
From: [EMAIL
question of the century :)
the same situation with Orca, it has version 3.1.3790., and all zeroes
are shown in the support info.
i decompiled Orca with dark.exe and can see that:
Product Id={85F4CBCB-9BBC-4B50-A7D8-E1106771498D} Language=1033
Manufacturer=Microsoft Corporation Name=Orca
I have a program I need to install that won't work without the VC 9.0
redistributable package. Can I simply add the necessary merge modules and
be done? Or is there more involved?
-
Check out the new SourceForge.net
Here's the info on how to do it from the new How To topic I wrote on this very
topic that should show up in the next weekly WiX build:
How To: Install the Visual C++ Redistributable with your installer
If your application depends on the Visual C++ runtimes you can include them as
part of your
Fixed a small wrapping issue below that made the code sample hard to read.
Neil
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns
Sent: Wednesday, June 18, 2008 9:57 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re:
Interesting! I am porting InstallShield project to Wix and I see that IS
keeps leading 0s.
-Original Message-
From: Neil Enns [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 18, 2008 12:23 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX and
Thanks Neil. Good information!
On Wed, Jun 18, 2008 at 1:00 PM, Neil Enns [EMAIL PROTECTED] wrote:
Fixed a small wrapping issue below that made the code sample hard to read.
Neil
-Original Message-
From: [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] On Behalf Of Neil Enns
Sent:
Thank you Alex,
dark doesn't insert asterisks in the version.
it's incorrect formatting, i wanted simply highlight version with bold in my
email client, but here
http://www.nabble.com/WiX-and-Support-Information-in-%22Add-or-Remove-Programs%22-panel-td17985802.htmli
see version between stars.
so
I see what you mean. I just did a quick test with product version set to
001.000.000..
When I opened msi with Orca, ProductVersion is set to 1.0.0.0. If I manually
change the product version back to what I have in the WiX file than I can see
all zeros in the ARP.
So, it seems like it is
Hello,
I am facing a strange issue here and any help to figure out what is happening
will be greatly appreciated. We released our product SP1 (build 6.0.6278.)
and then started work on SP2 build after few builds I noticed the file
sequencing has changed in the File table. Tracing back to
The way this works is that file version can be used to do an in-place update of
the assembly in the GAC. An assembly's file version defaults to its .NET
assembly version, but you can add an AssemblyFileVersion to give the assembly a
file version that's different from the assembly version. The
I'm just trying out WiX and still have a lot to learn about Visual Studio so
I may have made a stupid mistake here. I can't get WiX to appear under
Visual Studio 2008 standard. I have Visual Studio 2005 and 2008 installed.
It seems to work fine for 2005. When I did the initial install I was
Just to add to what Phil Wilson wrote:
The resulting MSI file will have a FileVersion row in the
MsiAssemblyName table.
Unless I am mistaken this will only be true if you use the -fv option to
light.
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED]
Thanks Heath, but unfortunately wix 3.0 Patch does not seem to support patching
files from MSMs (
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg12785.html ) and
going to wixlibs from MSM now means a complete overhaul of setup. I am pretty
sure something has changed on our
What version of the WiX toolset are you using? There are reports that changing
the .NET Framework version changes the sort order in WiX v2. WiX v3 is not
affected by this problem because the sorting algorithm was changed.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL
Yes, the version gets normalized down to numbers without extra zeroes. There
are bugs in the Fusion processing of version where they incorrectly treat
versions as strings and it was found that removing insignificant zeroes from a
version string would avoid them. At least, that's what my
MSI SDK has a list of reasons why SelfReg is evil.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of jeff sacksteder
Sent: Tuesday, June 17, 2008 18:02
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] self-registering
I'm trying to package a legacy
Alexander Shevchuk wrote:
So, it seems like it is WiX's problem. It changes ProductVersion by removing
leading zeros.
Please file a bug. The compiler core uses the Version class to validate
version information; it parses the string down to their component
integers, which loses the
Amy Rosewater wrote:
Schema validation failed with the following error: The element 'Control'
in namespace 'http://schemas.microsoft.com/wix/2006/wi' has invalid
child element 'Text' in namespace
'http://schemas.microsoft.com/wix/2006/wi'. List of possible elements
expected: 'Condition
Calin Iaru wrote:
I am doing a major upgrade and the Start Menu/Programs/OldEntry
folder is not removed. I would like to keep the OldEntry, but now, both
OldEntry and NewEntry exist in the Programs folder. Any ideas as to why
is the delete shortcuts action inhibited?
Check a verbose
Adrian Lewis wrote:
Not knowingly... Okay my extension has packaged the wixlib as an embedded
resource (and the wixlib has the custom action binding - not forgetting the -bf
switch to get it included in the build) is there somewhere else in the
extension where I'm supposed to inform WiX that
Rob,
This Fusion processing related to putting assemblies in GAC?
What we are seeing is that the value of ProductVersion property is getting
normalized, not assembly version.
Alex
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching
Sent:
Hi,
I have a powershell script which will be added into the MSI package. I want
to execute the script after installation completed automatically. How can I do
it?
Thanks a lot for your help in advance.
-
Check
Well in part because these have evolved for a while and I've been using them
for at least three years - possibly before wix.targets became part of the
product? And in part because I had no idea they were there :-/
I'm really glad you pointed this out, but it got me wondering (again) how I
missed
Hi Neil, Thanks for the response..
Yes, the log says..
MSI (c) (0C:28) [13:45:05:326]: PROPERTY CHANGE: Adding INSTALLLEVEL
property. Its value is '1'.
MSI (c) (0C:28) [13:45:05:326]: skipping installation of assembly component:
{646909B9-8B31-4429-9556-82AE57B3F4EE} since the assembly already
You can use it stand-alone, but it's also part of the Votive stuff that's
significantly reworked in WiX v3. Assuming you installed WiX v3 on a machine
that has VS on it you should be able to do File New Project... and then pick
WiX from the left nodes and create a new WiX project.
This is in
38 matches
Mail list logo
