none
Visual Studio 2017 does not see dependeny through symlink RRS feed

  • Question

  • Hello everyone!

    we have experiencing issues in our company with Visual Studio 2017 which is using dependencies located on network share. We have created a symlink which is pointing to that share and VS is using this symlink to locate the files. From some time (around 2 weeks), visual studio is unable to 'see' these files and during compilation we are receivng error: LNK1104 cannot open file "XYZ(...)". Of course all users have proper access to that network share and they can access it through windows explorer or total commander. The funny thing is that when we open the folder where those files are located, compiler will see these dependencies, it only fails when the folder is closed in windows explorer or in any other file manager.

    Does anyone of you have an idea how to troubleshoot this issue? 

    Thanks for help in advance!

    Arek

    Friday, September 20, 2019 1:16 PM

All replies