We have a lot of documents associated with our software development.   These include things like requirements, design documents, external PDFs, customer files, testing instructions, etc.  Currently, these documents are scattered all over the place (wiki, some place on the network, a local developers hard drive(!), and even worse places).What's the best way to keep track of them?  Since we use visual studio (2010) for our development, and we don't really have any non-developers on the project, I thought it'd be a great idea to store them within the VS solution, which would allow them to be source controlled, and universally accessible by all the developers.However, VS really doesn't seem to be built to do this.   If you edit any document file, even one that is setup with the build properties None, Do not copy, VS must will rebuild the software before it will run again.   There is no way to create a Documentation Project within the solution.  (We use an Empty C# project for this).  Visual Studio and Word/Excel flat do not do source control well.   You can't view a checked-in file, and then decide to make a change without first closing the file, going to the project, and manually checking it out before making the change.  It's slow and tedious at best.Anyway this is the best our team has come up with, but I really wish I had a better (free) solution.
What's the best way to store documentation associated with a code project?
version control;documentation
I'm not sure if there's a single best way, but from your description, it sounds like every developer is doing his/her own way of storing documentation. Get a buy-in from everyone on a single method of storing documentation, and it'll be a lot easier to keep it organized.Besides the find the best way for you answer, I'd say to at least look for a solution that makes it easy to search for documents. At one company, I set up a wiki that contained links to files thrown all about serverland, which suddenly made it much easier to search for and locate documents no matter where they were. Once other users started using the wiki to find documents, they also started updating it to either link new documents, or by just creating a wiki entry as the document.I'd love to hear from anyone else if they know about free version control systems that work well with documents. The only thing that comes off the top of my head is Sharepoint, which isn't exactly free. I've seen unofficial versioning systems where people have an Archive folder, and simply put past revisions of a file in that folder, with the newest revision being in the same folder level as Archive.