I have a file and a hard link to it. When I use Visual Studio 2013 IDE to save either the original file or the hard link, the hard link is destroyed -- I get two unlinked files.
Symbolic link ain't destroyed by Visual Studio 2013. But since its target is in the different directory a problem with TFS server workspace occurs -- I can't add the symbolic-link-file itself to a workspace; TFS plug-in tries to add the link's target which is out of the workspace mapping.
It looks like Visual Studio 2005 had the same issue: there's KB945993 (FIX: The hard link of a file is destroyed if you use Visual Studio 2005 to open and to modify either the original file or the hard link) describing exact the same problem but for the previous software version. The article describes the fix for 'msenv.dll' file. But my 'msenv.dll' from Visual Studio 2013 is older (I have version 12.0.21005.1, size 9.03 MB, date modified 10/5/2013 9:38 AM UTC). Anyway I believe a fix for Visual Studio 8 ain't applied for Visual Studio 12.
Also there's unanswered and archived thread on this forum: Visual Studio 2005 & 2008 break fsutil hardlinks.
Do anyone have a suggestion what should I do?
Thanks a lot!