this took me the whole morning to figure out that it's in fact the P4VS extension's fault:
When I launch my C# project from Visual Studio by pressing (Ctrl+)F5 it suddenly does not find some DLLs anymore that normally get loaded from various subdirectories.
It turns out that this occurs only after I open a Perforce connection with the project. I assume in the latest update of the extension there was some fiddling with working directories or DLL search order configuration introduced, which has some side effects propagating to processes launched from within VS.
Nasty bug introduced probably in 2020.1.193.5313
No replies to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users