> And I don't imagine Visual Studio Solutions for C# are used like this. At my workplace, we've just been cleaning up a whole bunch of instances of exactly tha

> And I don't imagine Visual Studio Solutions for C# are used like this. At my workplace, we've just been cleaning up a whole bunch of instances of exactly that anti-pattern. Except that it's obviously not symlinks (which require specific user rights on Windows), but links to external files in VS. Same problem, though: They're easy to introduce and a pain to deal with later on.