Windows

NAVIGATION
CATEGORIES
REFERRENCE
LINKS
  • WinNT ADSI provider

    0 answers - 1402 bytes - related search similar search Add To My Delicious Add To My Stumble Upon Add To My Google Mark Add To My Facebook Add To My Digg Add To My Reddit

    Not having to do an LDAP query prior to connecting to the user. So they
    will not have to store a lookup account and baseDN type info. I think
    that adding the LDAP features is pretty simple, but I don't want to make
    them do it if it's not necessary.
    Message
    From: ActiveDir-owner (AT) mail (DOT) activedir.org
    [mailto:ActiveDir-owner (AT) mail (DOT) activedir.org] Behalf Brian Desmond
    Sent: Tuesday, 17, 2006 2:16 PM
    To: ActiveDir (AT) mail (DOT) activedir.org
    Subject: RE: [ActiveDir] WinNT ADSI provider
    What simplicity will this offer?
    Thanks,
    Brian Desmond
    brian (AT) briandesmond (DOT) com
    c - 312.731.3132
    Message
    From: ActiveDir-owner (AT) mail (DOT) activedir.org [mailto:ActiveDir-
    owner (AT) mail (DOT) activedir.org] Behalf Isenhour, Joseph
    Sent: Tuesday, 17, 2006 4:02 PM
    To: ActiveDir (AT) mail (DOT) activedir.org
    Subject: [ActiveDir] WinNT ADSI provider
    I have a customer who wants to write their authentication DLL using
    the
    WinNT ADSI provider instead of LDAP provider for simplicity. Does
    anyone know if there will be any supportability issues with this
    option
    going forward? Is Longhorn going to support it?
    BTW, the app is written in vb6 so System.DirectoryServices is out.
    Thanks
    List archive:
    List archive:
    List archive:

Re: WinNT ADSI provider


max 4000 letters.
Your nickname that display:
In order to stop the spam: 3 + 2 =
QUESTION ON "Windows"

EMSDN.COM