When .NET serializes it will use the TypeForwardedFrom information when

writing Assembly information but Mono does not. This means that
serialized objects created on one platform are not able to be
deserialized on the other, thus preventing interoperability between .NET
and mono applications. Fixes the ObservableCollection part of bugzilla
11294.

Clear the domain on thread exit after the profile thread end hook, si…

…nce it might need it to be set.

Hopefully fix the windows build.

rx: Add -d:HAS_AWAIT options to 4.5 and 2.1 builds.

Fix the mobile build.

empty commit to get a new build going with a gtk-sharp fix

Fix space in makefile

Fix few warnings

Avoid deadce on OP_INEG since it sets the condition codes, and the OP…

…_LNEG decomposition depends on this on x86. Fixes mono#10320.

[msbuild] Fix import set to expected path when invalid imports are al…

…lowed.

It was failing to resolve <Import> to correct path because it allowed
invalid imports too early in Import.ForEachExtensionPathTillFound().

It is due to Project.AddSingleImport() that checks if invalid imports
can be ignored by load setting. But simply removing this check results
in regressions in nunit tests that fails to report required invalid imports.

This bug was one of the blockers to build fsharp-droid from xbuild:
https://github.com/fahadsuhaib/fsharp-droid