We usually check with the vendor (manufacturer) of the software to see
what their recommended approach is as we consider them to be the expert
on their software. Heck, you work at Microsoft, can't you ask someone
there?
-Original Message-
From: Subrahmanya Jagadeesh Madduri [mailto:j...@mi
I assume the silence of the last two days is either that none of us have
ever used it (or even heard of it, in many cases), or that the few that know
about it haven't discovered your message yet (and you need to give them more
time since they may not troll this list on a daily basis).
For you and
Hi,
I'm trying to detect whether the Windows Communication Foundation HTTP
Activation and Windows Process Activation features are installed. Anyone have
a good approach for this.
Thanks,
Jagadeesh
--
Come build
In XP: you either are an administrator or you are not. It is simple.
In Vista with UAC turned off: Same as XP.
In Vista with UAC turned on: Administrators are "not" an administrator until
they elevate (via the consent dialog). Non-administrators can also elevate
via the same mechanism by supplyin
Thanks for the help, I tried it without InstallPrivileges="elevated" and it
almost got it to work. Both methods ('Condition' element and type 19 custom
action) appear to have the same net effect.
XP works great and stops the install if not an admin. That fine and is what I
want. Vista howev
I'm trying to detect whether the Windows Communication Foundation HTTP
Activation and Windows Process Activation features are installed. Anyone have
a good approach for this.
Scott
--
Come build with us! The BlackBer
Can't you condition the features?
-Original Message-
From: jnewton [mailto:jonathan.new...@ni.com]
Sent: Friday, September 25, 2009 12:03 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Suggestions on Disabling a Feature if Certain .NET
Framework Isn't Installed
I have a fea
I have a feature tree that consists of several features that install .NET
support. So I have a tree like
".NET Framework 2.0 Support"
".NET Framework 3.0 Support"
...
What I would like to do is have those features either disabled or greyed out
if the Framework associated with that feature isn't
I'm trying to detect whether the Windows Communication Foundation HTTP
Activation and Windows Process Activation features are installed. Does anyone
know what these product IDs or regkeys are?
Scott
--
Come build wit
My preference would be to have the new MSI only include the new files,
however we could include older versions if necessary. Ideally the
versions in the GAC would stack up until someone uninstalls them. If we
could pull it off I would like to have one entry in add remove programs
that gives the op
It is a rule breakage no matter what, but those of us who have been in your
spot before have learned the side effects of several different rule
breakages, both short and long term.
When breaking component rules, major upgrades tend to be something you will
be forced to do sooner or later, and so i
I've been thinking about your situation. How are you generating your
language transforms?
-Original Message-
From: Gareth [mailto:gmor...@serif.com]
Sent: Friday, September 25, 2009 3:16 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Multi language patching
This is an e
The same InstallExecuteSequence is used for all of the following (you should
test):
Initial installation
Major Upgrade
Minor Upgrade/Small Update
Patching
Repair
Removal
You should test that your conditions work for all of those scenarios.
-Original Message-
From: Pally Sandher [mailto:p
I assume you mean C1 and C1-prime in step 2.
I have to refresh my memory on what is allowed in a Major Upgrade vs. other
upgrades. I think that moving R3 to C1-prime must only be allowed because
this is a major upgrade. Otherwise it breaks the rules? I suspect I will
always be doing major upgrad
Thanks again for the guidance Blair.
Our log contains an entry for each .dll:
ExecNetFx: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ngen.exe
install "C:\Program Files\Resolver One\bin\Controls.dll"
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version
2.0.50727.3053
ExecNetFx: Cop
Hi,
For people having the same issue, here is what I have found.
If there are new folders starting with dot "." ( e.g. folder name '.data' )
added to the upgrade image, installing patch will give the "Error reading
file" error dialog. If removing dot "." and changing ".data" to "data", the
patch
Right these are getting annoying now.
Are there no list admins around who can unsubscribe this address?
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 **
Integrated Environmen
This is an entirely manufactured situation for testing purposes - I don't
want to send out our first multi-language package without knowing how to
patch it. Boy, am I glad too!
We're currently looking at the language definitions and think we're going
along the right lines though.
Cheers, G
Bl
There is no such thing as "UnInstallExecuteSequence".
Schedule & Condition your action appropriately in the
InstallExecuteSequence. I suggest something like After="RemoveFiles" and
set the inner text to something like "REMOVE AND Installed" (note: those
are suggestions don't just use them without
v3.0.5419.0. Your v3.0 is very out-dated.
You won't be able to simply compile WiX v2.0 XML in WiX v3.0 by
upgrading your compiler. The schema has changed between v2.0 & v3.0. You
would be well advised to run your .wxs files through WiXCop.exe first
and/or re-harvest anything you previously harvest
Hi all,
what is the lateststable version of wix . we are using Wix 3.0.2925 version.
I think latest is 3.0.5295.
I have all my projects in Wix 2.0.2925. But they are not being compiled in
Wix 3.0.5295.
in wix 2.0.2925 in the project type , custom action project type is not
there.
I am bit confus
Create a custom action that triggers your command and schedule it using the
condition "Installed" in the InstallExecuteSequence after the sequence
position of the other custom program that iss sequenced during installation
(set that condition to "NOT Installed" to ensure it doesn't get ran during
u
Ok, the workaround did the trick.
Changed the component containing the Guid='*' to a generated guid and now it
builds.
Thank you!
--
View this message in context:
http://n2.nabble.com/RegistryKey-and-Property-Value-tp3705191p3711037.html
Sent from the wix-users mailing list archive at Nabble.c
23 matches
Mail list logo
