Jan Kotas

We are moving this project to https://github.com/dotnet/runtimelab/tree/feature/NativeAOT . The new place is fork of dotnet/runtime repo that has the build infrastructure for cross-compilation. Getting the NativeAOT branch building for x86...

This is caused by running in `x86 Native Tools Command Prompt`. Try running in vanilla command prompt or `x64 Native Tools Command Prompt`. We have this error mentioned in https://github.com/dotnet/corert/blob/master/Documentation/how-to-build-and-run-ilcompiler-in-console-shell-prompt.md#workarounds-for-build-errors-on-windows....

@MichalStrehovsky change may help with this crash. There is still a potential more fundamental problem: The regular Lock can end up using wait method overriden via synchronization context. The class...

cc @yowl

> `Marshal.SizeOf(typeof(SafeNativeMethods.BITMAPINFOHEADER))` You can submit PR to WinForms to change `BITMAPINFOHEADER` to struct and this line to `sizeof(SafeNativeMethods.BITMAPINFOHEADER)`. It has significantly better performance everywhere, and it is guaranteed to be...

Also, I have submitted the System.Drawing interop improvement as https://github.com/dotnet/runtime/pull/33967

#8143 has discussion about the implementation strategy for ComWrappers in CoreRT. These comments points to components that you may be able to reuse: https://github.com/dotnet/corert/pull/8143#issuecomment-626201188 https://github.com/dotnet/corert/pull/8143#issuecomment-635051591 > MenuStrip, ContextMenuStrip, ToolStrip, and...

The built-in COM support in classic .NET runtimes is not AOT friendly. It is not possible to reliably compute the set of COM interop wrappers that the application is going...

> I think we could make this return null Returning null won't make https://github.com/open-telemetry/opentelemetry-dotnet/blob/af2b551316e111665af277553ccd40f18079d276/src/OpenTelemetry/Trace/ExceptionProcessor.cs#L42-L77 work correctly. I am not sure what this code is trying to do exactly, but returning...

> Updated an ErrorMessage This error message is too specific. The package name does not matter for 503 errors. You can see it in the log file attached to this...