You're seeing the same thing many others of us dealing with 3rd party LDAP
hosts are. Evenyone is focusing on LDAP as it pertains to AD.
In the mean time most of our methods developed and proven under 1.1
framework are totally broken under 2.0.
I've got some fractured code working on my 3rd party LDAP host but still am
trying to fix problems with it.
This looks like a huge hole left in VS2005 most likely on purpose. As
beautiful as the data connector is on SQL stuff to leave the LDAP world
hanging like this says very little good. Very much "back of the bus" approch
to a core part of the majority of enterprises.
Will be happy to share when I get something worked out but I'm NOT a
application coder, I'm a web dev so it is a slow process.
"jfer" wrote:
I recently ported an ASP.NET 1.1 web application to ASP.NET 2.0 Beta 2.
This is a VERY basic application that utilized the DirectoryServices
namespace. However I cannot get it to work in asp.net 2.0. When I
launch the web application I receive the following error:
"Exception Details: System.Runtime.InteropServices.COMException: The
parameter is incorrect."
Anyone know if there is an issue with ASP.NET 2.0 and
DirectoryServices/LDAP?
Thanks