Basically :
- for "old" applications, with most packages MS provides a list of the files
that you are allowed to redistribute. You may have to include this DLL in
your package (and preferably using the "official" way). For example you may
have this for the various ActiveX controls that were provided with VB6.
- with .NET this is much less frequent as the framework is installed as a
whole once for all (opposed as letting each application installing the part
it needs)
- you may still have problem with older OS that won't support all .NET
classes but in this case it's likely a technical limitation and "installing"
the DLL likely won't change anything
To get back to System.DirectortyServices. This is part of the .NET
framework. If the .NET framework is installed it is available. You don't
have to install it. This is also the kind of thing that I believe won't work
on older OS (because they don't use Active Directory, the problem is not
that the DLL is missing, the problem is that the OS does not have the
"feature").
Let us know if you have a specific problem in mind...
Patrice
--
<ha*****@hotmail.com> a écrit dans le message de
news:11*********************@g43g2000cwa.googlegro ups.com...
Ok, so what if I was writing a vb6 application for windows 98 and by
default windows 98 doesnt come with the particular dll, the dll is part
of a microsoft package that you download from the MS website and
install?