My new project now has a reference to the original Helper.cs and any changes I make to it, from either project, are reflected in both projects.
Enjoy!-- DKDisclaimer(s):This posting is provided "AS IS" with no warranties, and confers no rights.
It seems like this would have an adverse effect on the ease of sharing projects between developers, as it would require, potentially, having to acquire additional projects that perhaps you really don't care about. I think I'd honestly prefer doing the extra work of moving that file into it's own assembly over linking to a file in a potentially unrelated project. Or, at a minimum, moving it to it's own, separate folder, and linking to it from both projects, instead of reaching from one project into another.David Kline: In the case of sharing projects, a separate assembly is my preference as well. I typically use file links for simple, small projects where I am the only developer.
Just wondering does this work well with TFS Build?
Does the shared file required to be a part of a project. Because I have an instance where my C# file will not be a part of the project but it is a generated file and then many projects utlize the same file.
Now I tried the same approach of Add as Link but the VSS does not reflect the link file. How do I achieve that since I am using VSS 2005 and not VSTS?