views:

325

answers:

4

I have written a class that will handle internal logging in my application. Now I want to use this class in another new and totally separate project.

I could simply copy the file to the new project folder, but I would like to only have one copy of it to maintain so that all changes in it will apply to both projects over time.

I can use the "add existing file", but where do I put the file so that the next developer knows that it is required. I have once had a "shared" folder for this but one time that folder was not brought into the next development computer.

What is the best way to organize this so that it makes most sense for new maintainers and minimizes the risk for broken links in projects.

+5  A: 

You could create a library project that has this class this way all you have to do is add a reference to that project...

Petoj
+3  A: 

Break your logging code to a seperate assembly.

You can then include that assembly in the projects that should use that logger.

It keeps everything nice and clean and you'll only have to maintain one set of code rather than having to worry about each copy.

Justin Niessner
+1  A: 

Create a new assembly that contains this class.

Then all your other projects can refer to this assembly and use the class within.

Mongus Pong
+2  A: 

A class library to share is the best solution.

But you can add a file to a VS project as a link rather than copying. To do this use the drop down on the Add button of the add existing item dialogue.

Richard