Only PE binary files (normally .EXE, .DLL, .OCX, .SYS, etc.) files carry
version resources that Windows Installer knows about. Other file types
(.TXT, .INI, .XML, .CAB, etc.) files that are not PE binary files can't have
the version resource Windows Installer knows how to read and have to use the
Regarding paragraph three... I don't have any trouble with my
product/upgrade codes working. They are all set and upgrades to
specific products work great.
The trouble is that I need to upgrade a file that is shared between
about 30 *different* installers. It's a common dependency between
these
Hi Blair,
I got the issue in my service itself. Thanks for your reply.
-Sanjay
Blair wrote:
Default value is no. On a test computer, if you use the sc create
command to register the service, and then start it, does it still stop upon
logoff? If so, that would rule out Windows Installer/WiX as
Now we might be getting somewhere.
When binding source files into a wixout the field values associated with wix
extensions are missing extra properties/decorations.
Wixout from a working version contains this
table name=WixControl
xmlns=http://schemas.microsoft.com/wix/2006/objects;
row
When iam trying to create the installer i am getting the following error.
The directory ProgramMenuDir is in the user profile but is not listed in the
RemoveFile table.
How do i resolve this issue?
below is the directory structure i am using.
Directory Id='TARGETDIR' Name='SourceDir'
Add an additional RemoveFolder element targeting ProgramMenuDir in your
ProgramMenuDirMonarch component. There is no limit to the number of
RemoveFolder elements you can have in the same component.
-Original Message-
From: subrat agasti [mailto:subrat.w...@gmail.com]
Sent: Wednesday,
It gives me some good clues. I like your workaround idea, BTW. There is a
benefit to only shipping an RTM version of an MSI and only releasing updates
to that via MSP (it can simplify to some extent your testing and deployment
matrix).
-Original Message-
From: Matt Sullivan
This is an old thread now, but I thought I'd update to mention that I've just
seen this on Windows
7. The PATH var is updated and can be verified in the env var management
window, but a new command
prompt does not see the update. Opening the env var management window and
clicking OK fixes
Hi,
Thanks for the reply.
However, I already have a structure similar to the one outlined by you:
Control Id=BannerBitmap Type=Bitmap Text=WixUI_Bmp_Banner ../
Control Id=SomeText Type=Text Text=Enter the ..: .. /
Control Id=SomeEditBox Type=Edit Property=SOMEPROPERTY
Text=[SOMEPROPERTY]
Hi everybody,
I'm trying to use WIX to generate a patch for an installer created using
Visual Studio 2008. It's a simple patch that updates a single file. I
started with an all-wix approach using pyro. After some trial and error I
managed to create a patch. When I install it however I get an
Hi All,
I have a installer which installs large number of files(~5 files).
It takes a lot of time to install. However it's installation time is
tolerable.
But while upgrading it takes intolerable amount of time(more than 1 hour
sometimes). It also takes lot of time(1 hour) in un
Hi,
We use msi installer for our software and we are using WIX toolset for that.
After upgrading to newer version of our software sometimes users of our
software does not find themselves convenient with new version and they
want to go back to previous version.
Is there any mechanism in WIX for
Hello,
I suppose this question was asked before, but i couldn't find a clear
answer for it:
When an installer runs on the target machine, and installs all the files
in the InstallDir, i would like to carry some extra actions.
-Get a config file that was installed, i.e foo.config.
-Modify that
Hi,
I am very new to WIX. When i am trying to create an msi i am getting the
following error.
Unresolved reference to symbol 'Directory:SystemFolder'in section
'fragment:'
I have created the .wxs file using heat.exe. I know that there is no
systemFolder diretory in my directory structure.
But
WiX != Windows Installer. You would do well not to confuse them or use
them interchangeably.
If you're using Major Upgrade functionality remove the Upgrade table
entries and/or your Launch Condition which block installing an older
version.
If you're not using Major Upgrade functionality, educate
but my newer version of application generates/modifies some files in
installation directory at target machine which may not be appropriate
for older version. These files not present in installer. these files are
generated when application runs after installation. I want these files
also in
If the file is installed as part of your installation you can simply use
it's Id as a Property e.g. [#foo.config] if you set Id=foo.config in
it's File element (see -
http://msdn.microsoft.com/en-us/library/aa368609.aspx). Use that
Property as the path for either XMLConfig or XMLFile to make your
Then your installer should've been written with cleaning up those files
in mind before you released it and/or those files which need modified
after install shouldn't be held in the installation directory if it's a
per-machine installation, they should be in CommonAppData or somewhere
similar as
I modified WixAdvancedSample.wxs to build for 64 bit arch.
Unfortunately, it's installing on the 32 Program files folder:
?xml version=1.0 encoding=utf-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Product Id=49d75c41-17e3-48ed-9f4f-e65cedd3285e
If I put files in CommonAppData, In that case also files generated by
newer version are not valid for older version. Is there any way to
backup older files/setting up a restore point for a particular directory.
Pally Sandher wrote:
Then your installer should've been written with cleaning up
Change the HelpDirectory attributes for the TypeLibs in the pasted code
which point at SystemFolder to point somewhere else such as
dir07B00FE80C030860241E2DB3BAF7AE7D (that's an example, might not be
correct for your COM DLL's).
heat.exe generates sample code, you shouldn't expect to be able to
So what is the conclusion? That what I am trying is basically impossible?
I tried setting the action to Impersonate=No and Execute=Commit. I got this
for my trouble:
---
Action start 13:54:36: LaunchConfig.
MSI (c) (AC:A8) [13:54:36:027]: Note: 1: 2762
DEBUG: Error 2762: Unable to schedule
Check a verbose log?
Is your MSI built for the x64 platform? Open it in InstEd/Orca check
the Summary Info. The Platform property should be set to x64 or AMD64
(both are the same thing, latter is deprecated by the former).
Palbinder Sandher
Software Deployment IT Administrator
T: +44 (0) 141
Thanks Palbinder.
On the summary info, the platform property is set to x64.
The verbose log doesn't show any errors:
Generating database.
Merging modules.
Validating database.
ICE01: ICE01 - Simple ICE that doesn't test anything
ICE01: Created 04/29/1998. Last Modified 08/17/1998.
ICE01: Called
This is a known issue with *Windows Installer* patching upgrades.
Windows Installer WiX are not the same thing.
I'm guessing you're using Major Upgrades to upgrade (correct me if I'm
wrong). Take a look at a verbose log when upgrading or uninstalling
see where it's taking so long. My guess will
Try using QTExec as per the example at
http://wix.sourceforge.net/manual-wix3/run_program_after_install.htm but ignore
the parts about adding the checkbox text to the ExitDialog if you don't want
them (and modify the Condition of the example Publish accordingly).
Palbinder Sandher
Software
Thanks Pally,
On the summary info, the platform property is set to x64 and the verbose log
doesn't show any errors.
Cordialement / Best regards,
Gernot
-Message d'origine-
De : Pally Sandher [mailto:pally.sand...@iesve.com]
Envoyé : Wednesday, July 07, 2010 2:03 PM
À : General
On 7/7/2010 7:50 AM, Gernot Kerger wrote:
I modified WixAdvancedSample.wxs to build for 64 bit arch.
Unfortunately, it's installing on the 32 Program files folder:
Known bug with workaround:
https://sourceforge.net/tracker/?func=detailaid=2793021group_id=105970atid=642714
--
sig://boB
On 7/4/2010 11:30 AM, Adi Sashkis wrote:
I read that theutil:CloseApplication / might be what i need but I am not
quit sure how it's works.
Use the property you give it as a condition, either a dialog or an error
custom action to prevent installation when set (i.e., when the process
is
Try a verbose log from when you *install* the product not build it.
Palbinder Sandher
Software Deployment IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the Virtual Environment**
Integrated Environmental Solutions
The file is installed by the installer, so i can use [#foo.config].
When i thought of doing this approach (XMLConfig || XMLFile), i got
stuck because:
I want to do the foo.config editing after a specific dialog, i.e
EnterConfigurationDlg, so that
i can grab the PROPERTIES from that dialog and
The file is installed by the installer, so i can use [#foo.config].
When i thought of doing this approach (XMLConfig || XMLFile), i got
stuck because:
I want to do the foo.config editing after a specific dialog, i.e
EnterConfigurationDlg, so that
i can grab the PROPERTIES from that dialog and
-I changes product code everytime. I do not changes upgradecode.
after splitting it into two msi files is there any way to combine them
into single file, so that user do not need to download two files and
install them separately.
suppose I have two msi files
1. constant.msi
2. variable.msi
I
Hi,
I am faced with a problem of building an MSI that requires a set of
directories to be created during installation. These directories are
all prefixed with a common string (eg folder) followed by a sequence
number (eg 01) so that their final construction might be something
like folder01,
XMLConfig XMLFile don't make changes in the InstallUISequence, only in
the InstallExecuteSequence so using the contents of Properties from the
UI sequence should be fine. Are you setting your Properties to be
Secure? If you want to pass information in Properties from the
InstallUISequence to the
Can we use a single MSI installer on both platform(32 bit and 64 bit) ?
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first --
On 7/7/2010 8:05 AM, Thomas Due wrote:
So what is the conclusion? That what I am trying is basically impossible?
MSI will not launch an elevated process except as a deferred custom
action and you can't use those from the UI.
--
sig://boB
http://joyofsetup.com/
You'd need to use a bootstrapper for that. Until Burn is done WiX
doesn't have any support for this. I would recommend dotnetinstaller
(http://dotnetinstaller.codeplex.com/) but other bootstrappers are
widely available.
Palbinder Sandher
Software Deployment IT Administrator
T: +44 (0) 141 945
An x86 MSI will install on x86 x64 platforms.
An x64 MSI will only install on x64 platforms.
You cannot write to x64 locations in an x86 MSI. Windows Installer
simply does not support it will stop you in your tracks if you even
try it.
Essentially your question is far too vague for a simple
after splitting it into two msi files is there any way to combine them into
single file
You'll need to use a bootstrapper program to achieve this. The bootstrapper
would package up both MSIs, check to see if constant.msi is already installed
(and install it if not), then install
Okie...
simple and direct question
what is the default value of 'platform' attribute in Package element ?
Thanks for all your help.
Pally Sandher wrote:
An x86 MSI will install on x86 x64 platforms.
An x64 MSI will only install on x64 platforms.
You cannot write to x64 locations in an x86
Are there tools to monitor an installation and then generate a
WiX-compatible project/wxs?
An example of the need for this is to monitor the execution of an old
installer that is not in MSI format with a goal to convert that
installation to a WiX project which can be used to generate an MSI
Short answer.no.
But if you just need a single installer, look into using a bootstrapper
which can run either your 32-bit or your 64-bit MSI depending on the
environment it's being installed into.
On 07/07/2010 09:07 AM, Sanjay Rao wrote:
Can we use a single MSI installer on both
Depends what you select for platform when you build your MSI.
Palbinder Sandher
Software Deployment IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the Virtual Environment**
Integrated Environmental Solutions Limited.
Thanks Bob,
How would I have to set APPLICATIONDIR then?
I tried:
SetDirectory Id=APPLICATIONFOLDER Value=[ProgramFiles64Folder] /
Cordialement / Best regards,
Gernot
-Message d'origine-
De : Bob Arnson [mailto:b...@joyofsetup.com]
Envoyé : Wednesday, July 07, 2010 2:42 PM
À :
dark.exe can decompile an existing MSI but the output from it is overly
complex includes everything in every table in the MSI (including UI
which often you don't want/need as the WiX UI will be more than
sufficient). It also doesn't clean up the code it decompiles so you
will find a lot of
Hi,
I have an installer that is supposed to include installing a group of customer
specific documents. I would like to install the root directory of this
document tree, which will copy all subdirectories and files to a specific
folder on the target device. I do not want to itemize each file
You can use companion files to force your non-versioned files to update
properly.
http://msdn.microsoft.com/en-us/library/aa367997(VS.85).aspx
You'll have to manage the companion relationship between the non-versioned
files you want to update and the versioned file you are referencing. This
On 7/6/2010 2:51 AM, Matt Sullivan wrote:
Does anyone know why building a patch that uses a binary diff would fail with
error 2725 (invalid database tables) when the exact same patch built without
works fine?
There was a bug in delta patching recently fixed in WiX v3.5. Try the
latest
Doesn't matter which version of WiX you're using, it's not possible
using Windows Installer. heat.exe or some other custom solution in your
build process will be required. If you're using Windows Installer, you
have to explicitly list each file directory you want to create on the
target machine.
-Original Message-
From: Beth Hechanova [mailto:bhechan...@imsco-us.com]
I found a few references to using heat. I tried that out, which seems to
generate a wxs fragment with the proper list of files and subdirs. So perhaps
that can be integrated into my automated build, but how
My automated build uses cruisecontrol.net, nant, and candle/light to build my
installer via the .wxs file. I do not have a .wixproj file. My application
has two different installs - one for the application code (executable, dlls),
which will be used by all customers. The other installer is
Actually I think what needs to be done is to add the -svb6 option to
heat's command line. The items that are asking for the SystemFolder happen
to be related to the VB6 runtime.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Wednesday, July 07, 2010 4:57 AM
Hi,
Does the driver uninstall put an entry into PendingFileRenameOperations
in the registry?
http://technet.microsoft.com/en-us/library/cc960241.aspx
If so you could check this key is clean before running the install, I
have implmemented this in the past.
Dave
-Original Message-
From:
When I generate wxs sources using heat I treat it as a build product. I do not
keep the generated file in source control. I dynamically add the generated file
to the ItemGroup that contains the wxs source files to compile. An ItemGroup is
similar in concept to a fileset in NAnt.
I personally
My recommendation would be to add an immediate custom action in the
InstallExecuteSequence table before CostInitialize that adds temporary
rows to the DuplicateFile table and temporary rows to the Directory table.
You would also need the following authoring:
InstallExecuteSequence
I ran into the following error today with a DTF Custom Action assembly I am
working on.
The custom action assembly has 17 entrypoints, which is more than the maximum
(16).
Refactor the custom actions or add more entrypoint slots in SfxCA\EntryPoints.h.
I grabbed the latest copy
Is there a way to set permissions on a Directory element. I know there's a
CreateFolder element, but the folder will be created already as part of the
installation. It doesn't seem like there's an obvious way to do this...
(Basically my scenario is that I need to set some permissions on my web
If you write an immediate custom action to schedule deferred and rollback
actions, then you've already used up 3 slots right there for one logical custom
action. Add an equivalent set of 3 actions for uninstall and you've consumed a
total of 6 slots for a single logical operation pair.
I
Use CreateFolder. It doesn't hurt anything to ask for a folder to be created
that will be created anyway.
-Original Message-
From: Alec Siu [mailto:alec@microsoft.com]
Sent: Wednesday, July 07, 2010 2:37 PM
To: WiX Users List (wix-users@lists.sourceforge.net)
Subject: [WiX-users]
Hi All,
Is there a way to apply a transform during package installation (using
custom action, for example). Or how can I change msi tables during runtime
(during installation).
p.s. I understand this is not directly a wix related question, I will
appreciate any response. Thanks.
Best Regards,
You can add temporary rows with a custom action. That and setting Properties
are the only mutations allowed that I'm aware of.
On Wed, Jul 7, 2010 at 8:15 PM, gulfam murad gulfam.mu...@gmail.com wrote:
Hi All,
Is there a way to apply a transform during package installation (using
custom
Any body have any idea about this ?
Sanjay Rao wrote:
If I put files in CommonAppData, In that case also files generated by
newer version are not valid for older version. Is there any way to
backup older files/setting up a restore point for a particular directory.
Pally Sandher wrote:
Thanks Rob!
So, if we used embedded language transforms to support MUI (
http://www.installsite.org/pages/en/msi/articles/embeddedlang/). And there
is a bug in one of the language transforms (e.g. ServiceInstall table has
some wrong information), what are my options to resolve this issue? Thanks
64 matches
Mail list logo
