TFS 2008 and linked classes at 10.9.09

At the company were I used to work we had a lot of shared classes (check this article for more info on shared classes) for all the apps we develop. When I started there in january I asked why they did not have any form of version control. They told me that this was because both vss and tfs could not handle the shared classes. At the time I did not have time to research this, but today I found a few extra minutes.

I made three projects, of which two in the same workspace, created a class in the first project and added the same class as link to the second project. When I added the class as link I got the following warning

.. Ok, now this seems to make sense.. I have both projects in the same workspace so it should not be neccesary to change the bindings..

So far so good... Let's try and change the class in the second project and check in the change from within the second project:

As you can see in the picture above, the path is to the first project...
Change is checked without any problem, let's see if it is really changed in project 1:

It is changed. Ok, so the argument of not having tfs because it cannot manage shared classes is not entirely valid. Let's see what happens when I try to add the class of project one to the third project:

Conclusion

So the shared classes should be preferably in the same solution. If this is not the case, you can still add the class as link to a different solution as long as it is in the same workspace!