This is not an "answer" because the problem seems to be a bug in Visual Studio/Visual D in my case. BUT it is a WORKAROUND if your conditions match mine.
In my case I get the similar message about:
D:\Program Files (x86)\VisualD\msbuild\dcompile.targets(382,11): error MSB4057: The target "ComputeLinkImportLibraryOutputsForClean" does not exist in the project.
AFTER successful build operation which in fact writes out the desired executable.
My conditions are VS 17.9.6 on disk D:, project all C/C++ with one linked library referenced, either X64 or Win32. I have Visual D installed, which seems a factor in the error.
Option 1:
Check your "Output" tab to see if the build outputs the .exe file properly. If so then following workaround can get past the error message when debugging:
Since output of the .exe is successful before the crazy error message, it asks "Would you like to continue and run the last successful build?" I hit yes and continue to successfully debug my program, with the latest updates compiled.
If previously the build succeeded before the error, and you are only debugging again, you have to remember that the error is spurious and you won't see the build output the .exe file. But just continue as above and should work.
(In my case I don't get this error message if the build actually failed before output of the .exe, I get the actual failure issue presented and this case would not apply. If building a release copy not debugged, just ignore the message if the output tab shows successful creation of exe or other targets before the error.)
Option 2:
I uninstalled the entire Visual D application using Windows 10 "Aps & features" on control panel. Seems to resolve the problem (of course no longer have D language available). I see reference to this problem in the Visual D GitHub source, and suspect that updating to latest version of Visual D will also fix the problem (but have not tried yet).