By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,446 Members | 2,998 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,446 IT Pros & Developers. It's quick & easy.

Source file path

P: 17

I have a problem with managing source files in VS 2005, I hope someone could help me out.
There are a few source files I'd like to keep global for all my projects.
I use tortoisesvn so I can keep them under versioncontrol.
I have to keep the files in a seperate directory to make this work (due to svn).

So far so good, yet the problem arises when I want to add a file from the seperate directory to my visual studio project.
It seems VS automatically makes a copy of the file to its local project directory, and keeps it that way.
If I look at the "full path" property of the file in VS, I can see the path has indeed changed to the local project directory and a new copy of it has been created locally. This is a problem as it negates the version control system.

Does anyone maby know how this copy-thing can be turned off, or how to change/keep the source-path? The full-path property is greyed so I cannot changed that..
Any help is much appreciated.

Sep 6 '07 #1
Share this Question
Share on Google+
3 Replies

P: 17
Solved it myself.

For anyone who's also been strugling with this: it's possible to add a file as a link. This is the way to do it.
This is possible through: "Add Existing Item..." and then there is a dropdown menu available on the add button! (well. that's not very obvious!). You can choose "add as link there"...
Dang. That was not easy to find.
Sep 6 '07 #2

Expert 5K+
P: 7,872
You should consider making a DLL of those common functions and then just referencing that?
Sep 6 '07 #3

P: 17
You should consider making a DLL of those common functions and then just referencing that?
Well, it's for using code which is shared, used and updated by multiple users. Hence the subversion thing.
Dll's would work if there's only one user. The nice thing with this is the code is always up to date, is easily compiled within each project, is completely transparent (unlike dll's) and easily updated by a user if necesairy (without having to compile a seperate dll). And since it's stricly about global code a version difference shouldn't matter.
Thanks for your input though.
Sep 7 '07 #4

Post your reply

Sign in to post your reply or Sign up for a free account.