Upgraded my project from 2017.1 to 2017.3 and now I cannot build for windows. I’m able to play the game inside of unity without issue. I am not getting error that is descriptive (at least for me). All I seem to get is simply “error building: 2 errors”. Is there something I am missing? There must be a way to dig deeper and find out what the issue is. What am I doing wrong?
Attached a snippet showing my console whenever I try to build.
[Edit]
Solved, see post #3
[Update]
I think I may have found something related to this issue. I think that unity uses mono to actually build the player instead of visual studio. Visual studio doesn’t kick back any errors at me when I build so I tried switching the project to mono editor. Now mono is giving me 2 errors; the same amount the unity console is when it tries to build the player. I think these might be related. I don’t have a solution for this /langversion; issue yet though.
[Edit]
I was able to get those 2 errors to go away inside of mono by switching to .Net 4.6 but the original errors still persist when trying to build the player in unity.
[Update 2]
If I let a normal build fail, then switch to development build + script only, I can build an .exe just fine. Still an issue because I will need release builds at some point.
[Update 3]
I made a separate identical project so I can start slimming it down until it builds. Removed the entire plugins folder and deleted code that referenced anything from plugins. Still nothing, 2 build errors with no description. This is totally absurd.
After deleting basically everything one by one in a copy of the project I found the cause of my cryptic build errors.
[SOLUTION]
This is more voodoo than anything else. This probably only applies to you if you use the Forge Networking library from the asset store like I do for my project. I had gotten a warning about a prefab object containing more than one transform, namely BMSLogger from said library. After simply selecting the prefab, expanding it, and closing it again, the project now builds without error.

This is the prefab in question. Just click the arrow to expand it, maybe click some doodads in the inspector for it, and then watch your project just magically work again.
[Edit]
I haven’t seen any side effects from just deleting that prefab and the script attached to it. That may be easier.
Hi cschoenig,
I am getting the same messages have been pulling my hair out because of this and only just found this post. Many thanks for posting this, I will try your solution.
Kind regards,
J