It can be done via the ServiceInstaller.vb -- but "supposedly" Microsoft are
not going to support his option in Vista (we shall see). But I recommend
that you avoid using Interact with Desktop as it is NOT reliable if your
service shells or uses Diagnostics.Process.
The irony is that Microsoft's Auto update service uses some undocumented
"features" that don't seem to be available to anyone else without really
digging deep (and I do mean deep).
Good luck, but if you can avoid any interface interaction via your service,
that really is the more stable/predictable and future proof route. My
personal belief is that this is just BS on a stick as and "interface" exists
as soon as the freakin' windows logo is displayed (but the Microsoft fan
boys will somehow argue this is not an interface so don't believe your eyes
and start subscribing to a religion). this limitation in Vista is there as
a non-intelligent blanket approach to attempt to make the OS more secure.
M$ are going about it the 1/2 half-ass lazy way -- as usual.
And I'm trying to be nice to Microsoft about this topic.
"screwy" <sc*******@hotmail.dewrote in message
news:11**********************@p79g2000cwp.googlegr oups.com...
screwy schrieb:
>Hi! I've been trying to figure out how to enable desktop interaction
support for windows services from within my vb.net code desperatly, but
wasnt able to find anything useful. Does anyone know how to do this?
Thanks in advance for your help!
Well, writing this post helped me a great deal modifying my search
phrase to finally find something useful:
there's a thread in
http://groups.google.de/group/micros...nguages.csharp
dealing with this problem. Here's the link to it:
http://groups.google.de/group/micros...373d0c48851f22
