Matt_Taylor

I have found that code written for .Net 1.1 to perform LDAP queries of Active Directory using the System.DirectoryServices library fails on a server that only runs .Net 2.0. Apparently the DirectoryEntry.get_Password() getter was depricated between .Net 1.1 and 2.0 (http://groups.google.co.uk/group/microsoft.public.adsi.general/browse_thread/thread/6cde11ed85cc4ead/02c1a1b48331ebc8 lnk=st&q=%22DirectoryEntry.get_Password%22&rnum=1&hl=en#02c1a1b48331ebc8).

The code I have written runs perfectly in an ASP.NET 2.0 application on a test server that also has .Net 1.1 and 3.0 installed (even though from what I have read it shouldn't !) but the production server is only running .Net 2.0 and 3.0. My question is are there any known issues with retrospectively installing .Net 1.1 on such a server (I'm not convinced this will resolve the issue anyway which is why this is an absolute last resort).

Thanks for any help you can give me.

Matt



Re: .NET Framework Setup Known issues installing .Net 1.1 on Windows Server 2003 (enterprise) that is already running .Net 2.0 & 3.0?

Aaron Stebner

The .NET Framework 1.1 is installed as part of the OS on Windows Server 2003, so you should not need to install it at all on that OS. You may need to go to Add/Remove Windows Components, then select Application Server, then click Details in order to configure ASP.NET 1.1 for use with this server.

Thanks! Aaron





Re: .NET Framework Setup Known issues installing .Net 1.1 on Windows Server 2003 (enterprise) that is already running .Net 2.0 & 3.0?

Matt_Taylor

The issue here seemed to be the fact that the server is 64bit. IIS would have to be switched into 32bit mode to run ASP.NET 1.1 so I have sought another solution.

Thanks