The BS that is MS
If I hit build or debug the code works fine. But if I try to publish, I get this BS.
When I go to the tmp file, I get this BS.
9/23/2019 11:49:19 AM
System.AggregateException: One or more errors occurred. —> System.Exception: Build failed. Check the Output window for more details.
— End of inner exception stack trace —
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at Microsoft.WebTools.Publish.PublishService.VsWebProjectPublish.<>c__DisplayClass43_0.b__3()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Publish.Framework.ViewModel.ProfileSelectorViewModel.d__202.MoveNext()
—> (Inner Exception #0) System.Exception: Build failed. Check the Output window for more details.<—
System.Exception: Build failed. Check the Output window for more details.
Why send me to the temp file, just to get a message that says go to the output window. Just dump this to the flipping output window.
Finally, I go to the output window, and see
CSC(0,0): Error CS0006: Metadata file ‘C:\MyCode\My.Root\src\My.IdentityProviderServiceExtenders\bin\Release\netcoreapp2.2\win-x86\My.IdentityProviderServiceExtenders.dll’ could not be found
CSC(0,0): Error CS0006: Metadata file ‘C:\ MyCode \Lcp.Fortify.Root\src\My.Public\bin\Release\netcoreapp2.2\win-x86\My.Public.dll’ could not be found.
So I go to those directories, and I see the files that it is claiming don’t exists. So More BS!!!
- So WTF can I clean the whole solution, build and debug, but the publish cannot seem to do the same?
- Also WTF do I have to bound through 3 locations, 4 windows, to get this information?
This is why NodeJS is going to obsolete MS, and I suspect this is why so many people have jumped onto the VS Code bandwagon rather than using VS everywhere.
UPDATE: 8/9/2020
I don’t know what fixed this, but it eventually fixed itself. Meaning either an MS server patch, or a VS patch fixed it.
