I'm trying to migrate my existing ADSI code from VBA into NET 2.0.  Does
anyone have any ideas on what I should start using?  I'm trying to check the
status of my IIS server accross the network, which I as able to do
successfully in VBA.  I also read where you could use ADO and the special
provider to enumerate/fetch the status of your IIS://, LDAP://, WINNT://
type objects.  I wonder what you can use now in NET 2.0 to replace these
functions, since I can't get any of these instructions to work, despite
using the traditional GETOBJECT functions.  Is there a new ADSI replacement
provider in NET?  Please help!!!

First off, I'd STRONGLY recommend ditching WinNT and using LDAP:// for
all your operations (unless you have to work with user and groups on a
local machine). WinNT is deprecated and only provided as a backwards
compatibility kludge - don't use it for new stuff.

Furthermore, with .NET 2.0, you should definitely look at using the
DirectoryEntry and DirectorySearcher classes from the
System.DirectoryServices namespace - they are your best bet to get at
objects in AD, including searching for them - don't use the old-style
ADO searches and these things anymore.

As for info - there's a TON of stuff out there, and I'd recommend
starting with the S.DS portal on MSDN:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sds/sds/portal.asp

It has tons of docs, descriptions, and dozens if not hundreds of
VB.NET samples, too.

If you have more specific questions - you should direct your questions
to the microsoft.public.adsi.general newsgroups - that's where all the
DirectoryServices gurus hang out :-)

Cheers!
Marc

Binary representation of a double?
Possible bug with SerialPort Parity.None and/or ParityReplace
not able to read an XSD file
WebRequest and Range Header
app.config files and MMC snap-in