Sorry!
But I have forgot to say that in Windows XP all work correct.
It problem is in Windows 7.
Best Regards,
Fedor Pranovich
--
WatchGuard Dimension instantly turns raw network data into actionable
security
I've determined that this cannot be it, as I tried it on a machine and found
that the file was missing without doing any reboots. Thanks for the thought,
though, Scott.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade
Hi Phil, thanks for answering.
I don't think this is it; Windows installer 4.x is on Windows 7, correct?
That's the target here (though the symptoms appear on Vista as well). In any
case, this install does not use the GAC. (It does do the implicit program
files - program files (x86) map,
I understand and agree with what you said.
One would think that Feature container and references assure proper isolation.
If MSI does not support that wix compiler should (i.e. inject extra condition).
Instead wix silently accepts erroneous, or at least, very misleading construct.
Thank you
Ahh, very subjective that. There are a great many different ways this can go
and your suggestion is only one of them. More importantly, it sounds like you
may still be in transition from thinking procedurally to declaratively. This is
old blog entry of mine mostly about XML but a little about
What would you inject? Conditions on the Feature can be just about anything.
For example, I have a Feature in one project that is conditioned on the
existence of ADFS 2.0. If ADFS 2.0 is not installed, the Feature is disabled.
The corollary to that is that all the Components of that feature
I have setup a burn bundle that should installer the .NET 4.5 framework if it
does not exist. I works in some cases, but not in others. I posted a question
on Stackoverflow.com with the details:
http://stackoverflow.com/questions/21196507/prerequisite-not-running-on-condition-failure
If anyone
Pilot error is just a euphemism for an error in the MSI. If the
component is transitive, for example, it's presence depends on the
value of a property that may change in different scenarios. There may
be a custom action or other code that removes it. There's just a lot
of scope for things to
That reminds me, actions should always (with rare exception) be conditioned
based on Component states not Features. Thus those action should be in the same
Fragment as the Component (which they probably are below).
I've not run into many cases where I'd use Feature states in conditions.
Assuming I understand what you're doing, it won't work on Windows 7.
The short story is that you are not impersonating, therefore you are
trying to run something with the system account and have it show UI on
the interactive user's desktop. I don't think you are allowed to do
that in a UAC world.
Now that the .NET team finally has released a usable version of the event
source at
https://www.nuget.org/packages/Microsoft.Diagnostics.Tracing.EventSource
with v 1.0.16 - one that also supports the admin channel - the task is on me to
get it into some of our programs.
I am stuck in the
To be clear, in my example both the Feature and the Components are conditioned
on a public property loaded by a registry entry. I have used Feature states,
but only to control UI dialog flow.
--
John Merryweather Cooper
Build Install Engineer – ESA
Jack Henry Associates, Inc.®
Shawnee
If EventManifest can't do it, it'd be ideal to help improve it rather than one
off your own custom action. smile/
-Original Message-
From: Thomas Tomiczek [mailto:t.tomic...@nettecture.com]
Sent: Thursday, January 30, 2014 10:44 AM
To: General discussion for Windows Installer XML
UI flow, that is a place to use Feature conditions. I've forgotten about that.
I've moved to Burn based UI for everything myself. smile/
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Thursday, January 30, 2014 10:47 AM
To: General discussion about the WiX
That error indicates the type could not be updated. My first guess is that it
signifies something internally going awry.
-Original Message-
From: Bruce Cran [mailto:br...@cran.org.uk]
Sent: Thursday, January 30, 2014 11:07 AM
To: General discussion about the WiX toolset.
Subject:
Thanks everyone for the advice ! SuppressSignatureVerification=yes worked
for this user.
Another tidbit is that he was running the EXE as admin, and interestingly
the UAC prompt showed unknown for the publisher name. When I try the same
thing I see a prompt with our company name.
I'm tempted
If his machine doesn't have up to date root certifiates then the UAC prompt
isn't going to be able to verify the bundle executable any better than the
payloads. smile/
We're actually considering removing the Authenticode signature verification
inside Burn due to issues like this. The benefits
17 matches
Mail list logo
