Could not identify method in a referenced DLL?

Question

2.00/5 (1 vote)

See more:

I've an existing solution called Portal.sln which contains more number of projects. HLS.Common is one of the projects. I've added some .NET reference DLLs to the Common project (System.DirectoryServices and System.DirectoryServices.Protocols). I've added a public class and implemented a public method in the class.

I create another solution and refereed the HLS.Common DLL. While trying to access the newly created method I get error as given below.

Error 1 The type or namespace name 'HLS' could not be found (are you missing a using directive or an assembly reference?)

How to resolve the issue?

My code is shown below.

C#

    using System;
    using System.Collections.Generic;
    using System.Linq;
    using System.Text;
    using System.DirectoryServices; 
    using System.DirectoryServices.Protocols; 
    using System.Net; 
namespace HLS.Common.LDAP
{
    public class LDAPCommunicator
    {
        public bool VerifyLDAPConnection()
        {
            try
            {
                //Some logic here to connect with LDAP return true; 
            }
            catch (Exception e)
            { return false; }
        }
    }
}

In the client, in main method below code is used. In using statements using HLS.Common.LDAP is added.

LDAPCommunicator ldapCommunicator = new LDAPCommunicator();
bool result = ldapCommunicator.VerifyLDAPConnection();

Posted 10-Oct-12 21:22pm

Member 3137078

Updated 15-Oct-12 7:07am

Akinmade Bond

v2

Add a Solution

Comments

Sushil Mate 11-Oct-12 3:34am

Have you added the reference correctly?
Have you import the namespace in using statement?

Sergey Alexandrovich Kryukov 11-Oct-12 3:44am

Import? Using statement has nothing to do with namespaces (it is only related to IDisposable). You mix it up with using declaration:
http://msdn.microsoft.com/en-us/library/was37tzw.aspx
It simply changes the naming, has nothing to do with assembly referenced. You first question to OP is quite correct.
--SA

Sushil Mate 11-Oct-12 4:45am

i mean to ask in a different way.. :)
anyways thanks for correcting me..

n.podbielski 11-Oct-12 3:34am

Can you paste your code?

Oshtri Deka 11-Oct-12 3:35am

Have you tried to remove and add reference again?

Member 3137078 11-Oct-12 3:39am

Yes. I've added the reference correctly. I've added using statement correctly.

I removed and added the DLL again but no luck.

Member 3137078 11-Oct-12 3:42am

In HLS.Common the code is:

<pre>using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.DirectoryServices;
using System.DirectoryServices.Protocols;
using System.Net;

namespace HLS.Common.LDAP
{
public class LDAPCommunicator
{

public bool VerifyLDAPConnection()
{

try
{

//Some logic here to connect with LDAP
return true;

}
catch (Exception e)
{
return false;
}
}

}
}</pre>

In the client, in main method below code is used. In using statements
using HLS.Common.LDAP; is added.

<pre> LDAPCommunicator ldapCommunicator = new LDAPCommunicator();

bool result = ldapCommunicator.VerifyLDAPConnection();</pre>

Sergey Alexandrovich Kryukov 11-Oct-12 3:45am

Did you reference the assembly? How?
--SA

Member 3137078 11-Oct-12 3:49am

By selecting 'Add Reference' option of the client project and selecting the HLS.Common.Dll from the appropriate path. After adding the reference I viewed the DLL in Object Explorer and it contains the method VerifyLDAPConnection(). No issue on that.

Sergey Alexandrovich Kryukov 11-Oct-12 11:46am

"Add reference" windows has tabs ".NET", "Projects", etc. If you create some assemblies in your projects, I advise you to put them in the same solution. Why two your assemblies are in different solution, not in a different project of the same solution as it should be?

Can you draw all relevant dependencies and list all references of each? The resolution is somewhere there. What do you call "Common project"? If you create two assemblies, one depends on another, each may or may not reference, say, System.DirectoryServices and System.DirectoryServices.Protocols. You need to show all dependency and reference structure to sort it out. It should be something really simple. But first of all, I recommend adding the projects creating two different assemblies
--SA

Silent Guardian 15-Oct-12 14:51pm

Did u build the dll after editing?
There are chances that u might have missed it.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2012-10-15T07:50:00

You're adding a reference to the .DLL directly instead of the project for that .DLL.

When you make a change to the .DLL project and recompile, your reference to this .DLL is no longer valid as it relies on the version information in the assembly.

If you add a Project reference instead of browsing to the .DLL, this problem disappears. The problem with this is that you have to add the .DLL project to the solution containing your app holding the reference.