You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
I assume you tried under PowerShell. Apparently buildins from cmd.exe (the original windows shell) are not available by default in PowerShell. In your case there are 2 options (sorry for the incomplete reference in my last post):
mklink from a normal (cmd.exe) shellcmd \c mklink from a PowerShellDeveloper mode is a windows 10 thingie so you shouldn't worry about it. This report shouldn't have any impact on creating release builds (unless you are planning to introduce symlinks in the code base).
At the moment the impact from this report is probably pretty low. Depending whether or not symlink usage under windows starts snowballing (due to increased usage of certain package managers and symlink heavy git repositories for instance) it could become a usability issue.
One other note.
When setting up to provide a 3rd column to show behaviour when using shortcut files (*.lnk) I noted that the link is dereferenced upon opening showing the target. Although it prevents the problem stated in this report it might add to the confusion (why do .lnk files dereference and symlinks not).
It could off course also be intended behaviour, but for completeness I wanted to include this.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.