Update/To answer my own question:
I decompiled the .NET framework function
System.Diagnostic.EventLog.CreateEventSource and looked at the source code
for the WiX extension and confirmed that there was a discrepancy.
I then created a test project with .NET framework debugging turned on, s
I have raised a bug for this and attached logs and source:
https://sourceforge.net/tracker/?func=detail&aid=2951181&group_id=105970
&atid=642714
Neil
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: 10 February 2010 22:07
To: General discussion for Windows Inst
Hi Blair,
Thanks again for your advice. Sadly the late scheduling causes too
many other problems like updated files being removed. So I'll just
give up on the idea of cleaning up the registry. Not too important.
I really wish Windows Installer provided some kind of procedural
mechanism. I can app
On 2/9/2010 2:47 PM, Tony Juricic wrote:
> Since my external UI is WPF I am really bothered, both by having to
> disambiguate several classes and by having to reference forms Dll just for a
> few enums, when calling Installer.SetExternalUI. Hopefully these enums will
> become UI-system-agnostic
On 2/9/2010 12:04 PM, Jakub Gwóźdź wrote:
> But the more I think of them (and read on the web) the more scared I am.
> Since the only dlls installed in WinSxS comes from Microsoft (on a few
> computers I've checked so far) I'm starting to wonder why it isn't a
> popular solution.
>
Note that e
On 2/10/2010 11:50 AM, Tabmow wrote:
> Is it possible to change the error dialogs for some of the known types?
> Ie. If i know a certain Windows installer error code, can i override the
> default error dialog with my own dialog from my wix code?
>
No but you can use control conditions to
On 2/13/2010 4:02 AM, Joergen Bech wrote:
> So I guess the WiX way is fine and I should not care about the Sources value
> not being updated explicitly by WiXUtilExtension.
>
Right. When I wrote EventSource, I went by the Windows documentation.
--
sig://boB
http://joyofsetup.com/
-
On 2/12/2010 6:19 AM, John Aldridge wrote:
> If I use WiXNetFxExtension to test for NETFRAMEWORK35, does this mean
> "3.5 itself is installed" or "3.5 or any later version is installed"?
>
The former but it's not practical to make generalizations for future CLR
versions since they can be side
Okay, thanks very much Bob.
--
View this message in context:
http://n2.nabble.com/Change-the-error-dialog-upon-a-known-error-code-tp4549153p4567236.html
Sent from the wix-users mailing list archive at Nabble.com.
--
SOL
saschabeaumont wrote:
>
> As you shouldn't be modifying the system outside of the
> InstallExecuteSequence anyway I can't see how this would be a problem?
>
>
It's not a problem, so much as we prompt a few screens of required info
before the "Install" button is hit. Why have a user fill in
Igor Paniushkin wrote:
>
> Does it fail on installation?
> And as Sascha said that after pressing of the install button user will be
> prompted to enter a username and password, but you should be sure that you
> specified Impersonate="no" property on deferred custom actions which
> require admin
That's why there are custom actions.
Updated files shouldn't be removed if the component rules are followed with
late scheduling (in fact, updated files being removed is a sign that the
component rules are not being followed).
-Original Message-
From: Sebastiaan Deckers [mailto:c...@pandi
-Original Message-
From: Tabmow [mailto:tabmo...@gmail.com]
> It's not a problem, so much as we prompt a few screens of required info
> before the "Install" button is hit. Why have a user fill in these few
> screens only to find out they have wrong permissions? In the past, we
could
>
13 matches
Mail list logo
