Jerry,

OK, if you only need the DLL in your solution then yeah, that will work. I thought you needed the source code as well. My bad .... <g>

~~Bonnie



>Bonnie,
>
>Thanks for the reply.
>
>Actually, it looks like if I turn my class into a DLL then add that DLL as a reference to my solution, then build my solution, this seems to work. My solution will make a copy of the classes .dll but it'll do this everytime I rebuild my solution. So, my solution will always get the latest version of my class library.
>
>So far this looks like the way it works.
>
>Thanks,
>
>Jerryt
>
>
>
>>Jerry,
>>
>>As far as I know, you can't do what you want. The way we handle that is with SourceSafe. We actually *do* have two copies of the class on our PC (one for each solution), but they are the same file in VSS (they are shared in VSS) and so when you check-in or check-out any changes, it doesn't matter which solution you've made the changes in.
>>
>>I don't know how to do this (or if you even can) if you're not using some kind of SourceCode manager like VSS.
>>
>>~~Bonnie
>>
>>
>>>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