Hi All,
I want to show one UI dialog when user tries to uninstall the application
from add/remove panel.
How can I do this in WIX?
Does any one know this?
Thanks,
Hukum
--
The NEW KODAK i700 Series Scanners deliver under
Hi All,
I have created the WIX installer. In this problem is installer progress bar
is inconsistent.
So How I can make it consistent or move it according to my need?
Thanks,
Hukum
--
The NEW KODAK i700 Series Scanners
I will harvest a .Net COM dll and typelibrary (tlb) and had this working
earlier when I understood that I had to use the registration values instead
of Class-tags.
However I now recognize that the recent version of heat creates all the
registry values underneath HKCR while using the older build
Wilson, Phil a écrit :
If the UpgradeCode for Crystal is reliable you could make an Upgrade table
entry for it with only search for the range of versions you expect -
that'll set a property you can use in a type 19 custom action.
Mmmh... I have to admit I am far from being an expert in
Hi everyone,
I have noticed that heat will harvest a folder and all subfolders and put the
files in individual components. While following the tutorials, I had learned
that generally you put all files that reside in the same folder into a
component together, as long as they're your atomic
HKLM\Software\Classes is the same as HKCR.
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com mailto:n...@x2systems.com
From: jballe [mailto:j...@visionpeople.dk]
Sent: Wed 13/05/2009 10:30
To: wix-users@lists.sourceforge.net
Subject: [WiX-users]
Hi
I think the reason is that by using one file, one component you should be
able to upgrade a component with a new release upgrading package and leave
the rest non-changed files, so the installation will be a lot faster as
unnecessary deleting, uncompressing og copying files can be avoided.
Well you are probably right that it *should* be the same.
However when the other system (MS Dynamics NAV) tries to use the COM
component it can find a non-usable component without any name, when the
registries are written to HKCR and the things are working when the
registries are written to HKLM.
I don't know where to do that.
-Original Message-
From: Eric St.John [mailto:eric.st.j...@hotmail.com]
Sent: Tuesday, May 12, 2009 8:44 PM
To: wix-users
Subject: Re: [WiX-users] Localization file
Have you set wixlocalizati...@culture to en-US for the localization
files you expect to
Is it possible to preserver registry settings on major upgrade and only
delete it on uninstall?
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a
My WiX project installs a .Net 2.0 assembly into the GAC on install, however
when I uninstall, the assembly remains in the GAC. Anyone have any pointers
to how I go about removing the assembly from the GAC on uninstall? Is there
an option similar to the RegistryKey 'createAndRemoveOnUninstall'
I don't think this is the problem, try navigating to the keys in the registry
to confirm what I am saying. Having said that there is some redirection on 64
bit OSs, which OS are you seeing this in.
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com mailto:n...@x2systems.com
Great Work Brian!!
I just incorporated WiX 3.0.5308 into our build and harvested all 128 VB6
COM DLLs. Your fix works like a charm:
[exec] heat.exe : warning HEAT5156 : Ignoring the registry key
'Interface\{F3DB7AC0-A581-48C6-A973-8860578A77E1}\ProxyStubClsid/', it has
already been added
Hi,
I've been working on properly supporting feature selection (Custom
installs) in our packages. So far so good, except I've got a slight
conceptual problem.
I install into 2 different directories, both of which are user-
configurable. So my WXS looks kind of like:
Directory INSTALLDIR
Do I have to have a localization file if this is only going to do en-US
and inhouse? When I do a search for localization I'm not seeing
information on how to include the wxl file.
-Original Message-
From: Eric St.John [mailto:eric.st.j...@hotmail.com]
Sent: Tuesday, May 12, 2009
You need a component to have an individually serviceable element because the
decision MSI makes on whether or not to update/repair a file is based on a
component's keypath. If you have more than one file in a component and you
want to patch the file that is not the keypath you will be forced
Hey Roy,
Thanks for the positive feedback and metric data!
I am curious, does your installation package, once installed, work
correctly?
Thanks,
Brian Rogers
Intelligence removes complexity. - Me
http://icumove.spaces.live.com
On Wed, May 13, 2009 at 8:30 AM, Roy Abou Assaly
Open up your WXL file and look for the line like this:WixLocalization
Culture=foo xmlns=http://schemas.microsoft.com/wix/2006/localization;
Codepage=1252
Replace foo with en-US.
Date: Wed, 13 May 2009 10:23:02 -0400
From: james.macdiar...@eds.com
To: wix-users@lists.sourceforge.net
Subject:
Hey Jesper,
Can you file a bug for this? Tomorrow is the last night to fix bugs on
heat.exe. Please give me the full Component/ element or better yet the
.tlb itself so I can duplicate.
Thanks,
Brian Rogers
Intelligence removes complexity. - Me
http://icumove.spaces.live.com
On Wed, May 13,
I assumed you were using a WXL file because you mentioned that my project
isn't loading my localization file.
A localization file (WXL) is required if you use loc variables in your setup
source: IE !(loc.xx).
A localization file is also required if you use an extension (like
Hi,
What is the correct way to install fonts using Wix?
I always get the is a Font and must be installed to the
FontsFolder-warnings.
Best regards,
Kim
--
*Kim Gybels
Software Developer
* kim.gyb...@metris.com mailto:kim.gyb...@metris.com
Tel: +32 16 74 01 01
Fax: +32 16 74 01 02
* Metris
Have you seen the RegisterFonts element?
-Original Message-
From: Kim Gybels [mailto:kim.gyb...@metris.com]
Sent: Wednesday, May 13, 2009 12:29 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Installing fonts
Hi,
What is the correct way to install fonts using Wix?
I always
Assuming there are no sharing issues keeping it installed, the typical reason
for this is that the actual assembly name details do not match the description
that ends up in the MsiAssemblyName table in the MSI file. This means that the
identity must be fully specified with name, publickeytoken,
I'm using a modified featuretree.wxs and keep getting this error. But I can't
seem to locate what's causing it. If I comment out the Tree control, it
continues without an error, although the names of the text controls are shown
instead of the text..
Can anyone tell me what's causing this
Hi all,
I have an install where it may need to run SQL scripts on up to 2 different SQL
servers. I feel pretty comfortable collecting the information for one of those
four with a UI screen, but I'm hoping to reuse the screen for all SQL Servers.
From what little I know about UI development
If you look at the Upgrade element in WiX you can use OnlyDetect - yes and a
property. That property will be set if the range of versions in the Upgrade
element is detected.
Alex Shevchuk has a type 19 example in his MSI-Wix blog,
I have installed WIX to a network drive and am trying to build it. I took care
of the System.Security.Permissions already by configuring .NET Framework 1.1
zone security for the local intranet to full trust but now I am running into
this error:
[loadtasks] Scanning assembly
I'm currently using setupbld to generate a setup wrapper. However when I
sign the output using signtool it corrupts the executable. Trying to run
the resultant exe post signing yields an error:
Activation context generation failed for ...\badsetup.exe.Error in
manifest or policy file
Get an MSI log to see what's going on. Look at all instances of
FindRelatedProducts to see if it's detecting your older product.
Why is REP after InstallFinalize? This is outside the audited actions, and one
of the consequences is that if the uninstall of the older product fails it will
Wilson, Phil wrote:
Get an MSI log to see what's going on. Look at all instances of
FindRelatedProducts to see if it's detecting your older product.
There are two sections of FindRelatedProducts in the log for the 1.1 version
upgrade installation.
MSI (c) (28:8C) [18:56:27:953]: Doing action:
Alex,
Use the Registry Search to read the values into Properties before the upgrade,
and use the Properties to write the registry settings.
Michael
From: Alex Ivanoff [alex.ivan...@shavlik.com]
Sent: Thursday, 14 May 2009 12:34 AM
To: General
I am trying to get a simple wix project to install on IIS 6. I have WIX
3.0.5308.0 installed.
Here is the Product.wxs:
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:iis=http://schemas.microsoft.com/wix/IIsExtension;
Product
That means it didn't find the previous version for some reason otherwise it
would mention the ProductCode guid of the discovered product. What's actually
in the Upgrade table in the MSI file? I'm wondering if the version range is
really correct.
That location for REP is more efficient because
Your website element is a website locator (i.e. it has no parent component).
That means the CA will look for this website on the local machine to install to
(and fail the install if it isn't present), rather than create it if it doesn't
exist. The logs in this case appear consistent with it
This is what I am doing. I hoped there was a better way.
-Original Message-
From: Michael Osmond [mailto:mosm...@baytech.com.au]
Sent: Wednesday, May 13, 2009 14:43
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Preserve registry settings on upgrade
When I do a fresh install I'm using a bootstrapper to launch the msi
with admin rights so I can perform a LogonUser call in order to validate
the account used during the execution phase for the service. I want to
do that validation up front so I don't get an error during the execution
phase which
I go back to Wix Edit and change both the Product GUID and the Package
GUID.
The Upgrade ID GUID does not change. I rebuild the MSI setup package.
...
Upgrade Id=49AB249B-C143-412E-B138-6689533DC53A
UpgradeVersion Property=OLDERVERSIONBEINGUPGRADED
Maximum=!(bind.FileVersion.gssta_exe)
Wilson, Phil wrote:
That means it didn't find the previous version for some reason
otherwise it would mention the ProductCode guid of the discovered
product. What's actually in the Upgrade table in the MSI file? I'm
wondering if the version range is really correct.
From Orca, here are the two
And how about QWORD value?
-Original Message-
From: Alex Shevchuk [mailto:shevc...@live.com]
Sent: Tuesday, May 12, 2009 01:04
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] RegistrySearch and RegistryValue
Hi Alex,
Short answer: Yes, maybe, no.
That fixed it! Thanks!
-Original Message-
From: Wilson, Phil [mailto:phil.wil...@wonderware.com]
Sent: Wednesday, May 13, 2009 1:56 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Two Entries in Add or Remove Programs
That means it didn't find the
Schaff, Stephen wrote:
That fixed it! Thanks!
I think you replied to the wrong message, Stephen. The 'two entries' problem
continues.
--
Charles
--
The NEW KODAK i700 Series Scanners deliver under ANY
Opps, responded to the wrong email
So very sorry...
-Original Message-
From: Schaff, Stephen [mailto:stephen.sch...@aruplab.com]
Sent: Wednesday, May 13, 2009 4:20 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Two Entries in Add or Remove
The 'two entries' problem continues.
Well, if per-user/per-machine context did not change, I can only suggest
comparing your upgrade steps to steps in here:
http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-8-
major-upgrade.aspx
Alex
I have a wix project that creates a website. The certificate that that
website uses is already be present on the machine being installed to.
Is there a way to make the installer associate the website with the
existing installer? (I can do this step manually, but I would rather
have the installer
If I pass a property to my msi via command line, it seems like it is only
reflected in the current msi context but not when removeexistingproducts is
called to uninstall the old product. Is tehre any way to make this public
property pass to old msi as well?
--
View this message in context:
You could write an External UI handler. MSI SDK shows how.
Hukumchand Shah wrote:
Hi All,
I have created the WIX installer. In this problem is installer progress bar
is inconsistent.
So How I can make it consistent or move it according to my need?
Thanks,
Hukum
There was a thread about this recently. Think the summary was that this
is not possible.
Hukumchand Shah wrote:
Hi All,
I want to show one UI dialog when user tries to uninstall the application
from add/remove panel.
How can I do this in WIX?
Does any one know this?
Thanks,
Hukum
Yes. Features are a tree but Components can be duplicated throughout
as leaves as you want. In the end, a Component is installed as long as
one of its Features is installed.
Chris Ridd wrote:
Hi,
I've been working on properly supporting feature selection (Custom
installs) in our packages.
Not something we really support but did you make sure you trusted all of
the assemblies? Maybe that is the issue since it looks like the MMC
extension is failing to load.
Steven Chin wrote:
I have installed WIX to a network drive and am trying to build it. I took
care of the
In article 1242193011087-2879162.p...@n2.nabble.com,
achandrapano achan...@panologic.com writes:
What should I look for in the log file?
Call MsiProcessMessage immediately from your rollback CA to write
something into the log to confirm that your CA was indeed called.
effect. Is there
Hey Roy,
This is great news! Thank you for providing all the information to resolve
the bugs. I hope that this version will get you through until the next
version smile/. All further bugs will be held until feature works starts
then.
I appreciate your feedback and support while we addressed
If I pass a property to my msi via command line, it seems like it is only
reflected in the current msi context but not when removeexistingproducts is
called to uninstall the old product. Is tehre any way to make this public
property pass to old msi as well?
You need to preserve value of property
Alex Shevchuk wrote:
Well, if per-user/per-machine context did not change, I can only
suggest comparing your upgrade steps to steps in here:
...from-msi-to-wix-part-8-major-upgrade.aspx
I worked through that page of instructions. That resulted in a few changes.
In the Package element I added
Hi Charles,
Could you share your Product, Package, Upgrade, UpgradeVersion, and
InstallExecuteSequence elements? Also, context in which upgrade is
installed is the same as 1.0 version was installed, no changes in ALLUSER
property, right?
Alex
-Original Message-
From: Chuck
54 matches
Mail list logo
