As you can see from another answer, you can link the source code rather than
add existing.
I'm wondering, why not just compile the class into an assembly and reference
it from multiple projects? That's certainly the most "traditional" way to
do this, and it isn't more expensive in any way...
--- Nick
"Harry Whitehouse" <ha***@envmgr.com> wrote in message
news:O5*************@TK2MSFTNGP10.phx.gbl...
I'm developing a small class which will be used in a number of distinct
C# projects. This small class is undergoing constant change/refinement as I
try to employ it in the different projects.
I'm trying to maintain a *single* copy of the CS file that can be used in
the multiple .NET projects. But I'm observing that when you add a CS file
to a given .NET project, subsequent modifications to that file are only
saved in the current project.
Perhaps I've added the common CS file to the projects improperly. I went
to the righthand project node pane for project A and right clicked, selecting
Add Existing. Then I browsed to the directory for project B and added
this common CS file. But again, modifications to that file made when I'm in
Project A don't make it automatically to Project B.
If anyone has an idea of how to share a common source file over multiple
projects, I'd love to hear it!
TIA
Harry
