@JFMG some initial feedback:

mono_crash.*

Good catch!

// Just to be conform with the other folder name conventions
x64/ => [Xx]64/
x86/ => [Xx]86/

Any idea where this came from? I'm tentatively 👍, just wondering if there's extra context because x in these platform names has been a thing for a loooooong time.

// Visual Studio For Mac sometimes creates multiple bin and obj folders with increasing numbers, e.g. "bin 2/" (bin n/ where n = i + 1 and i starts from 0)

This feels like an uncommon scenario where the tooling might not be able to write to its preferred paths. I'm 👎 on this without more information or context for this behaviour.

@shiftkey

Good catch!

Thanks :-)

Any idea where this came from?

I wish I'd know 😅

This feels like an uncommon scenario where the tooling might not be able to write to its preferred paths.

Yep, this might be true. I've seen it a few times when Visual Studio for Mac and for Windows were in use. My guess is that in some cases the obj and bin folders get locked and therefore VS is not able to write into these folders. I didn't find any further information about this issue. It might be a bug in the tooling as you said.

@JFMG thanks!