By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,364 Members | 1,518 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,364 IT Pros & Developers. It's quick & easy.

System.Directoryservices being not recongnized

P: n/a
Hi,

I recently converted an ASP .net 1.1 project to 2.0 in VS 2005.
Even though System.DirectoryServices reference has been added to the
project, still for some reasons the Imports System.DirectoryServices
is not being recognized and there is a build time warning on it
stating:
Namespace or type specified in the Imports System.DirectoryServices
doesn't contain any public member or cannot be found. Make sure the
namespace or the type is defined and contains at least one public
member. Make sure the alias name doesn't contain other aliases.

Further there are build errors on all the classes belonging to this
assembly.

Does anyone else came across such an issue after conversion from old
version to new. Please share.

Thanks

Mar 28 '07 #1
Share this Question
Share on Google+
1 Reply


P: n/a
I just tried this to make sure and had no issue at all. Try deleting and then
re-adding the reference to System.DirectoryServices.
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"aa**********@gmail.com" wrote:
Hi,

I recently converted an ASP .net 1.1 project to 2.0 in VS 2005.
Even though System.DirectoryServices reference has been added to the
project, still for some reasons the Imports System.DirectoryServices
is not being recognized and there is a build time warning on it
stating:
Namespace or type specified in the Imports System.DirectoryServices
doesn't contain any public member or cannot be found. Make sure the
namespace or the type is defined and contains at least one public
member. Make sure the alias name doesn't contain other aliases.

Further there are build errors on all the classes belonging to this
assembly.

Does anyone else came across such an issue after conversion from old
version to new. Please share.

Thanks

Mar 28 '07 #2

This discussion thread is closed

Replies have been disabled for this discussion.