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
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-
From: Andy2k8 [mailto:appr...@gmail.com]
Sent: Tuesday, October 20, 2009 11:50 PM
To:
The thought that followed right after I pushed Send is that in your patch
you can change/remove that condition. The (updated) condition 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
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
you can change/remove that condition. The (updated) condition will be
I ahve a question regarding Installation Privileges and the setting of the
ALLUSERS property:
Is it possible to install an MSI in the allusers context without having admin
or any special rights (so be a normal user)?
cheers,
Tobias
--
Jetzt kostenlos herunterladen: Internet Explorer 8 und
Hello,
how can i create a window before ExitDialog window?
I want to show my own Dialog window (MyDlg) before ExitDialog window.
I am trying this but it is not functioning.
Publish Dialog=SetupTypeDlg Control=Next Event=NewDialog
Value=MyDlg1/Publish
I think, i am missing the right name of Dialog
Simple Answer: No.
Complex Answer: It depends on exactly what your installer does but the
things you can do are so limited they may as well not be possible
either. Hence the simple answer.
Palbinder Sandher
Software Deployment IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
Thanks for the quick response, so this was my first guess either.
So the other question is: is there a way to author a single installation that
can be isntalled in per user and all user context? The MSI MSDN help states
this is only possible for Windows 7 with MSI 5.0...
cheers,
Tobias
Date:
Using the functionality Blair described below you could have your
project build multiple versions of the same MSI, bundle them all with a
bootstrapper have the bootstrapper launch the correct one depending on
the users locale language settings. I haven't taken time to look at burn
yet but you
As Blair says UpgradeCode is only needed for Major Upgrades. Patches
don't need one (but you probably want to add one if/when you patch the
offending product so you can use a major upgrade if you ever have to in
the future). The WiX v2.0 help has a (very short) tutorial on creating
patches at
In stead of a bootstrapper - selecting the wanted transform - is it possible
for the .msi file itself to select a transform file? Maybe in a C++ CA?
Blair-2 wrote:
You get German since that is the first one in your list of Cultures.
MSI has never officially supported the scenario you
It is potentially possible to either allow the user to choose whether to
install per-user or per-machine by providing some method of setting the
ALLUSERS property such as a couple of radio buttons and you could take
the choice away from them if they aren't running as Administrator by
conditioning
Hi,
If you are using a wix project in Visual Studio, add a reference to the WIXUI
dll and add the code in. below is a sample that adds a custom dialog called
ServiceIdentityDlg.
UIRef Id=WixUI_Common /
UI
Property Id=DefaultUIFont Value=WixUI_Font_Normal /
TextStyle
Hi Wix - users,
I have developed one installer with Wix3. It is one upgradable
installer. It has defination about upgrade:
UpgradeCode=8517ae9a-667d-4bd3-9cea-4323be6d7040
Upgrade Id=8517ae9a-667d-4bd3-9cea-4323be6d7040
UpgradeVersion OnlyDetect=no Property=PREVIOUSFOUND
Minimum=5.0.0.0
We have a project that includes several wixlibs. These wixlibs all
export ComponentGroupRefs to one of two features in our main WiX
project. Installation appears to be working fine. But when I
uninstall the application, all of the components from one of the
wixlibs do NOT get uninstalled. When
hello
stop that
--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to
One thing to keep in mind as you go down this path is that the MSI database
is not a Unicode file. That means you can only put multiple languages in the
MSI that share the same code page.
virtually, Rob Mensching - RobMensching.com LLC http://robmensching.com
On Tue, Oct 20, 2009 at 5:12 AM,
Almost always and Action state of Null means you have a Condition that is
evaluating the Component out. The condition may be on the Feature or it may
be on the Component if the Component is marked Transitive.
If that isn't it, can you provide more detail about the Component and
Feature
I'd shorten Pally's answer to Not without a bootstrapper or MSI 5.0.
smile/
virtually, Rob Mensching - RobMensching.com LLC http://robmensching.com
On Wed, Oct 21, 2009 at 3:28 AM, Pally Sandher pally.sand...@iesve.comwrote:
It is potentially possible to either allow the user to choose whether
Unfortunately, no.
Have you read through the WiX tutorial http://wix.sf.net/tutorial? I
thought it had a nice section on languages in MSIs.
virtually, Rob Mensching - RobMensching.com LLC http://robmensching.com
On Wed, Oct 21, 2009 at 3:13 AM, mrtn mrtn.frederik...@gmail.com wrote:
In stead
1. Are you actually seeing your MSIs get generated with different GUIDs when
using the Component/@Guid=*? If so, that'd be a bug because it is supposed
to auto-generate *stable* GUIDs. That's why it took so long to implement the
feature. smile/
2. If you use the -gg switch it generates new GUIDs
We'd love to have it. Not a simply feature to implement. smile/
virtually, Rob Mensching - RobMensching.com LLC http://robmensching.com
On Tue, Oct 20, 2009 at 5:22 AM, Slide slide.o@gmail.com wrote:
Thanks for all the responses, I'll take a look at SharpDevelop and WixEdit,
although I'd
The New Install path you are talking about sounds like you need a
multi-instance MSI. Those are kinda' interesting to manage so I highly
recommend reading the MSI SDK topics about it.
On Wed, Oct 21, 2009 at 5:25 AM, Jiang, Chunyan (GE Healthcare)
chunyan.ji...@ge.com wrote:
Hi Wix - users,
ARPNOREPAIR affects the Add/Remove Programs (or Programs and Features as it
is called in Vista) in suppressing the Repair option. It has no other effect
on the operation of the MSI at all.
When building your patch, remove or change the REINSTALL = ALL condition
mentioned below or simply remove
Thanks for responding. Blair and you have both been very helpful. I'll
take a look at the link.
Regards,
Craig
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Wednesday, October 21, 2009 3:08 AM
To: General discussion for Windows Installer XML toolset.
Hi Rob,
Thank you for your suggestion.
I agree with you that I might need multi-instance. And I have read some
articles about multi-instance MSI, like
http://n2.nabble.com/Multiple-Instance-Transforms-Walkthrough-Proposed-Simple-Addition-to-WiX-to-Make-Them-Easier-td708828.html
Howver, it
So, then as I can not focus only on Windows 7, the bootstrapper would be
another way. What the bootstrapper should do at this side? As first I would say
it can check on Admin Rights to decide what installation can be done, but is
there anything else?
Will Burn Support this?
Cheers,
Tobias
Hi all,
I'm trying to create patch (service pack) for one product and I have a
problem with satellite assemblies (resources) which are installed in the
GAC, they should be updated by patch. After applying a patch only one
satellite assembly is updated, others are stayed not updated (old
version).
I believe that is the issue, though behavior is not what I would have expected.
Feature Id=AFEATURE
Title=title
Description=description
Level=1
AllowAdvertise=no
Condition Level=1![CDATA[XXX]]/Condition
Condition
Essentially you could do it within the same MSI without using a
bootstrapper.
Make duplicate components for anything which needs to be per-machine
condition the per-user ones with NOT Privileged while the normal ones
are conditioned with Privileged.
Then add them all to your Feature tree at the
Thank you Bob!
I have 5 edit boxes and couple labels and dialog description which
should be changed base on selected dialog. So next and back button
should have around 10 Publish events which will change values of such
indirect properties. So I doubt if it will be easier to maintain.
But anyway
For pretty much all Conditions the right answer is to have Installed OR
On Wed, Oct 21, 2009 at 8:12 AM, Tony yellowjacketl...@gmail.com wrote:
I believe that is the issue, though behavior is not what I would have
expected.
Feature Id=AFEATURE
Title=title
I have already my own dialog window (MyDialog) which is currently appearing
after license agreement dialog. For this i am using following code and it is
functioning.
Publish Dialog=LicenseAgreementDlg Control=Next Event=NewDialog
Value=MyDialog Order=2LicenseAccepted = 1/Publish
But now we want
When I run this in an immediate CA in the InstallUISequence
HRESULT hr = S_OK;
MSIHANDLE hTable = NULL;
MSIHANDLE hColumns = NULL;
MSIDBERROR error;
hr = WcaAddTempRecord(hTable, hColumns, LListBox, error, 0,
4, LPROPERTYNAME, 1, L0, LValue);
I get an hr
Hi,
In our product, after user1 installs the MSI, user1 will remove the original
MSI and then give the machine to user2. For example, the user1 installs the MSI
from a remote share and user2 will have no access to the remote share. This
will disable repair through add/remove program for user2
I'm working on some enhancements to our WiX based setup UI, and wanted to know
if a few things are possible using the UI components Windows Installer makes
available:
1) We have a custom action as a part of our installer that makes a web
service call. We'd like to embed in the UI a
Markus KARG wrote:
What I do not understand under this circumstances is: Why can I add a
LIST
of cultures to light.exe? I mean, what does it actually do with all
the
cultures if actually always taking just the first in the list?
It uses all of them to support fallback from available
Blair,
but what is the difference then between:
-culture:de,en
-culture:de;en
-culture:de,en;en
???
Thanks
Markus
It looks for the strings in all of the .wxl files sorting them in order
of
Culture, based on the order of the -Cultures parameter followed by the
order
the wxl files appear
Pally,
thank your for your introduction.
So if I understand correctly, if I want to provide multi lingual installers,
then either I must write a EXE that does the transformation, or I must
provide multiple MSIs and the user must choose the right one, or the user
must know how to use transforms?
Well, frankly spoken that (really huge) tutorial is in part outdated, false
and overly complex to understand, and it does things without explaining
their intension or details in some chapters (what really confuses
beginners). So after reading it two times I gave up and posted my question
here...
Hi Blair,
Thank you for your kindly reply. I really appreciate it.
Yes, I think checking the folder presence instead of checking the files would
work for us. I totally agree to use a built-in custom action instead of
supplying my own for the reliability. The reason we wanted to check
Hi Richard,
Thanks for your reply.
Additionally, you can't have more than one NewDialog control event on a
button, even if the conditions are mutually exclusive. - this is interesting.
Can you tell me where this fact comes from? I googled, it's not mentioned in
Wix or MSI. Also, I found this
Hi Markus,
I found this site is useful:
http://blogs.technet.com/alexshev/pages/from-msi-to-wix.aspx
I ever made a post Where to get more WiX
knowledge(http://n2.nabble.com/Where-to-get-more-WiX-knowledge-td3529191.html#a3529191
). But I was told to read MSI document. Well I even printed
hi all,
I have a Feature and i want to place a condition within this feature.
Example :-
the Feature is called SDK MAMAK Documentation. If the user selects this
feature a condition is invoked that will check to see if MAMAK is installed.
Only if MAMAK is installed will it allow the user to
What you can do is check to see if MAMAK is installed, and use that
knowledge to set a property. Then you condition the SDK MAMAK Documentation
feature itself to be disabled if MAMAK isn't installed. That would prevent
any and all components in that feature that are not in any other features
being
You did call WcaInitialize before calling WcaAddTempRecord, right?
-Original Message-
From: David Battey [mailto:dbat...@phoenixcon.com]
Sent: Wednesday, October 21, 2009 10:02 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] E_HANDLE returned from WcaAddTempRecord
When I run
You are on the wrong track in two ways: 1) the cached msi is a stripped msi,
and as a result it can't reliably repair the product, and 2) the registry
location you use is undocumented and subject to change and using it is not
supported by the Windows Installer team.
The right track consists of
Votive (actually the MSBuild scripts) differentiates between semicolon and
comma. It assumes the list separator is a semicolon and uses that to split
the list into separate invocations of light.exe, ignoring the comma. If you
change the default list separator character you may or may not break
Depending on where you read the information, different things come into
play.
In Votive (or anywhere else you are using the msbuild support), if you
supply the string de,en;en for the cultures setting (I don't remember the
casing or exact spelling of the property), you will get two MSIs built:
If you look in your generated InstallUISequence table you will see
ExitDialog as an action. If you want MyDialog to appear before it, you
would either effectively replace ExitDialog in that table with MyDialog and
call ExitDialog from your Next button, or you would insert your dialog
I gave up on msimsp/PatchWiz as soon as I had a viable alternative. It is
too big of a not-very-well-documented black hole.
Having said that,
http://msdn.microsoft.com/en-us/library/aa370346(VS.85).aspx says:
The MsiPatchOldAssemblyFile table and MsiPatchOldAssemblyName table are not
generated
Interesting. I've never heard that feedback before. Thank you.
On Wed, Oct 21, 2009 at 11:18 AM, Markus KARG markus.k...@gmx.net wrote:
Well, frankly spoken that (really huge) tutorial is in part outdated, false
and overly complex to understand, and it does things without explaining
their
1. Not that I know of.
2. Not that I know of.
Unfortunately, to get that kind of advanced UI, you probably will have to go
to an External UI handler. Note, that is a huge leap in terms of work
necessary.
On Wed, Oct 21, 2009 at 10:53 AM, Dan Giambalvo danie...@microsoft.comwrote:
I'm working
Hello,
In my installer that I created with Wix, I click a checkbox to accept
the license agreement and this enables the Next button. I want to do
the same with a MaskedEdit entry or two. That is, until both
MaskedEdit entries have at least X characters, I want the Next button
to be disabled.
Unless you have the person push some other button to call your custom
action, I have no idea how you would get your custom action invoked to check
the lengths to set the property needed to enable your Next button.
-Original Message-
From: kerbe...@noopy.org [mailto:kerbe...@noopy.org]
In article 664797.8163...@web59804.mail.ac4.yahoo.com,
little.forest little.for...@ymail.com writes:
Additionally, you can't have more than one NewDialog control event
on a button, even if the conditions are mutually exclusive.
At one point I found this buried in the MSI documentation; I
In article 664797.8163...@web59804.mail.ac4.yahoo.com,
little.forest little.for...@ymail.com writes:
Additionally, you can't have more than one NewDialog control event
on a button, even if the conditions are mutually exclusive. - this is
interesting. Ca n you tell me where this fact
Hi all,
I am doing Minor upgrade for my product. But Minor upgrade not replacing the
files.
Older ones are working fine.But the latest one is not working.
what are the causes, that fails the Minor upgrade.
Is it adding new files under some components?
Please advise some solution.
--
View this
Some questions.
What is your REINSTALLMODE value?
The files that are not replace: are they binary files with version
resources, or not? If not (such as text or xml) have they been modified in
any way?
You mention adding new files. These files were added to already existing
components? Did you
59 matches
Mail list logo
