netcommander�ë\¢iš�׫v+ºë¢{&‰ê貇ír‰

My .NET 2.0 app may need to call a shell to run Window Script Host scripts to
do some WMI work on a user's local computer. The computers are likely to be
based in peoples homes, rather than on a domain or corp. network.

Does the user have to be an Administrator to successfully have scripts run
in this way, or can a non-admin 'normal user' also have these scripts execute
successfully?

Would the fact that a script has been code-signed mean that it will always
be trusted locally, or might there be some Windows settings (e.g. in the
Registry) that might stop scripts executing on all machines?

Thanks.

netcommander�ë\¢iš�׫v+ºë¢{&‰ê貇ír‰

Hmm, possibly I could use .NETs System.Management namespace, but does it
cover all aspects of WMI, or just a subset?

asdf

"based in peoples homes, rather than on a domain or corp. network. "

Why don't you just have a good night sleep.

Dream of what you a capable of.

----------------------

Read a dictionary.

As in pre Orwellian Times.

-------------------------------------------

You have not, and problably can not post even a line of code
of wsh working slightly aside from script56chm.

-------------------

And this is not aggressive.

This is you on the 'couch'.

mayayana

One would hope it covers everything. You've got
a 70+ MB pile of .Net-specific dependencies when
you go with .Net. It's hard to imagine that you'd have
to resort to script for WMI support. But you might want
to ask in a .Net group about that.

microsoft.public.dotnet.general
microsoft.public.dotnet.languages.vb
microsoft.public.vsnet.general

If it were me I'd certainly want to avoid the scripting,
if possible. Script is generally less trusted than other
methods. Even if you don't have permission issues
you might have anti-virus issues. They tend to over-react
to script.