Problems with the last VS 2017 update

After the last update (8/18/2017) of VS 2017, every time I try to run my project I get the following

C:\Users\Michael\Desktop\New folder\New Unity Project\New Unity Project.csproj(263,9): error MSB3073: The command ““C:\Users\Michael\Desktop\New folder\Unity\Tools\AssemblyConverter.exe” -platform=uap -lock=“C:\Users\Michael\Desktop\New folder\New Unity Project\project.lock.json” -bits=32 -configuration=Release -removeDebuggableAttribute=False -uwpsdk=10.0.15063.0 -path=”." -path=“C:\Users\Michael\Desktop\New folder\Players\UAP\dotnet\x86\Release” “C:\Users\Michael\Desktop\New folder\New Unity Project\UnityEngine.dll” “C:\Users\Michael\Desktop\New folder\New Unity Project\UnityEngine.Timeline.dll” “C:\Users\Michael\Desktop\New folder\New Unity Project
unit.framework.dll” “C:\Users\Michael\Desktop\New folder\New Unity Project\UnityEngine.UI.dll” “C:\Users\Michael\Desktop\New folder\New Unity Project\UnityEngine.HoloLens.dll” “C:\Users\Michael\Desktop\New folder\New Unity Project\UnityEngine.Networking.dll”" exited with code 1.

There is a workaround for this problem.
when building the VS solution for the first time or when rebuilding it, VS creates project.lock.json files in the build folder.

Open those files in a text editor and exchange all instances of

Save the files and build (not rebuild, of course).

Unfortunately, this has to be done after every build from Unity as well as after every rebuild of the solution, until a fix is published.