linux-support | A set of Rust crates to make it easier to interoperate | File Utils library

Although it's only remotely related to programming, here it goes:

Since last week, I've been playing with Unity (5.6.0f3 Community x64) on Win 10 (x64) - using Visual Studio (2017 Community) as attached editor, as Unity "requires" -, and started with the [Unity]: Tutorials (first of them). For a few days everything went just fine, but then, building for PC Standalone target, stopped working. Googleing and checking the forums, didn't help finding information about this exact behavior:

As seen on the Build Settings dialog (moved to the right), there are no (Target Platform or Architecture) combo-boxes allowing to specify build parameters. Errors are on the left side.

Notes (about the current behavior):

• First guess was that the tutorial project became somehow messed up, so I created a new one from scratch (a dummy / simple one containing one Sphere having attached a Rigidbody and a C# script that applies forces based on user input), but it behaves the same (this is the project build output in the above image)
• WebGL build runs just fine (loads in browser); this is the workaround currently used, but it takes ages to complete
• Playing (obviously) also works (needless to say that things are OK in VStudio, no complains from csc), !!!but!!! after trying (and failing) to build, Playing no longer works (reloading the project is the only way to fix it)

To rule out any possible doubts, here's a DownloadAssistant screenshot:

Everything is checked, there are 2 items (not very relevant to this case) that are not showing (because the window is not sizeable), but they are checked (and installed).

Background info:

• When first installing Unity, there was no VStudio 2017 version present on the computer, so it (Community Edition) was installed as part of Unity install process (I remember (at least) one VStudio related combo-box in the Assistant)
• Then, a VStudio patch was available; when preparing to install it, I realized that VStudio was installed on the default path (on %SYSTEMDRIVE%), which doesn't work for me, since it's a large product, so:
  • Uninstalled it
  • Reinstalled it (directly from [VisualStudio]: Visual Studio Downloads) on a different drive (and yes, I am aware that changing the install path, still installs a pretty big part like Windows SDK on %SYSTEMDRIVE%)
  • Since I thought that the above 2 steps would break the link between Unity and the new VStudio, I also reinstalled Unity. This time, there were no VStudio related check-boxes in the Assistant (seems normal to check if any piece of software that it needs to install, isn't already installed ¹). Later on, I also found a persistent (meaning that it's not wiped out at Unity uninstall time) RegValue (HKEY_CURRENT_USER\SOFTWARE\Unity Technologies\Installer\Select_VisualStudio) with a value of 0 (as opposed to a bunch of other values under the same key with values of 1)
• After that, I reinstalled Unity several times, including reboots (not required) between uninstall / install, but no result (I also took a long shot of enabling the RegVaue above before starting Assistant)

A little debugging revealed that when trying to build (PC Standalone), Unity does something like this (don't mind the paths, it's how they're on my machine), that can be reproduced from cmdline:

build_win.bat:

...