You can do it this way or in your references, just change the default of Copy Local to false.

>Cathy,
>
>Thanks, I ended up creating a .DLL out of my classes soultion. I then added this .DLL to my application's solution as a reference. This still copies the classes DLL to my solution but it looks like everytime I rebuild my solution, a new classes.dll is created, ensuring that my solution always gets the latest version of my classes.dll.
>
>Does this sound correct to you?
>
>Thanks,
>
>Jerry
>
>
>
>>The other option is to create a separate project of the common classes and add the project to your solutions. There is an option for the project called "Copy Local". It defaults to True but you can change it to false to not have the dll copy to the main projects directory.
>>
>>Then of course, you could add your classes in a project then add them to the GAC, making them available for all projects
>>
>>>I am adding a class to my C# project. This class exists in a different directory.
>>>
>>>In my Solution Explorer I right click on my project and click on Add - Add Existing Item. I then navigate to the directory that contains my class.
>>>
>>>However, doing this creates a copy of the class in my current Solution's directory. So now I have 2 copies of myclass.cs.
>>>
>>>Is this the way it's suppose to work?
>>>
>>>How can I create a class library in one directory, add one of those classes to another solution but have that solution always look in the original directory for the .CS file?
>>>
>>>Thanks,
>>>
>>>Jerry