Dear all,
I am trying to add shortcut key associated with PushButton.
For example:
However, I found I could use not only but also or < A>
directly to push the button.
Is it possible to limit the shortcut key to only ?
Thanks
--
View this message in context:
http://windows-installer
I have been under the impression that MS hired some guy with 3 PhDs for
an R&D group. His project was cancelled and he was looking for work
elsewhere within MS. So, he was assigned to write the logger for windows
installer and MSBuild. He is so PO'd at being assigned such a trivial
task, he want
That's not a differential patch. Its a minor upgrade using the msi...
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Patches-and-using-instead-of-Component-Guids-tp7594909p7594962.html
Sent from the wix-users mailing list archive at Nabble.co
Hello All,
I have a question concerning the uninstall of a package. What should happen
to the user application runtime generated files of several users?
Here is what I got from the MS site for Best practices:
http://msdn.microsoft.com/en-us/library/windows/desktop/bb204770%28v=vs.85%2
9.a
I have a requirement to allow 'overwrite' of same version. I've tried
various combinations of , here is my current:
and in InstallExecuteSequence I have:
I think the 'right' thing to do is to require uninstall and then reinstall
'manually', but my requirement is to allow u
Instead of using the old Upgrade authoring, use the MajorUpgrade authoring and
take a look at the AllowSameVersionUpgrades attribute. Note that this is a
really bad idea(tm) in the field.
--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.®
Shawnee Mission,
I do this in some MSIs that we deploy strictly silently via Microsoft
system management stuff.
My upgrade block looks like this:
And also this, which I think matters:
Then I have a wxi file that I include that contains:
You don't really need the vars and the .wxi fi
Thanks, I'll take a look at that. I completely agree, this should not be
done but people more important than myself decide such things.
On Fri, May 30, 2014 at 12:09 PM, John Cooper
wrote:
> Instead of using the old Upgrade authoring, use the MajorUpgrade authoring
> and take a look at the Allo
My interpretation of using a file for user-specific data is that it's
being contrasted with using the registry. It is next to impossible to
remove HKCU-type registry data for a user that isn't currently logged
on. Removing a file in some other user's data folder is much easier.
We're talking about
Phil,
Thanks for the info, it clarified my assumptions...
Marc
-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: May-30-2014 12:37 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Uninstall Guidelines - What should be happening
My inte
Why is doing this a bad idea? I know that's the common belief, but I don't
know the reason.
On Fri, May 30, 2014 at 11:09 AM, John Cooper
wrote:
> Instead of using the old Upgrade authoring, use the MajorUpgrade authoring
> and take a look at the AllowSameVersionUpgrades attribute. Note that
1) Because you lose control over the particular ProductCode that represents
your GA/RTM installer. Now ANY installer built by ANYONE can be installed.
This exponentially increases the number of combinations you'll need to support
in the field. Not good unto itself. Pretty easy scenario too--
So it all comes down to multiple MSIs with the same version number causing
problems.
On Friday, May 30, 2014, John Cooper wrote:
> 1) Because you lose control over the particular ProductCode that
> represents your GA/RTM installer. Now ANY installer built by ANYONE can be
> installed. This exp
Conveniently timed blog post announcing a tool that sounds like it
might show the dependencies as MSBuild sees them:
http://blogs.msdn.com/b/vcblog/archive/2014/05/29/solution-dependency-viewer-extension.aspx
On Thu, May 29, 2014 at 8:20 AM, John Cooper wrote:
> Yes, but it's very messy and you
How do you do it? sample?
Thanks
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/how-to-create-desktop-shortcut-for-certain-groups-of-users-tp7594950p7594975.html
Sent from the wix-users mailing list archive at Nabble.com.
---
15 matches
Mail list logo