[wasm][aot] Figure out how to handle APIs not supported on AOT

[radical]

Some APIs, like Assembly.GetCallingAssembly() are not supported on wasm/AOT. We should have a clear behavior for this, eg. throw an exception, or maybe mark these APIs, so that the user is aware that these are not supported.

Example case: #53815

How is this handled for non-wasm+aot cases?

cc @vargaz @steveisok

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Some APIs, like Assembly.GetCallingAssembly() are not supported on wasm/AOT. We should have a clear behavior for this, eg. throw an exception, or maybe mark these APIs, so that the user is aware that these are not supported.

Example case: #53815

How is this handled for non-wasm+aot cases?

cc @vargaz @steveisok

Author:	radical
Assignees:	-
Labels:	arch-wasm
Milestone:	-

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[steveisok]

/cc @akoeplinger

[lewing]

We could make a mono AOT analyzer that look for attributes when AOT is enabled, I'm not sure there is a more general way to solve this. It would apply to mobile scenarios too.

[lewing]

#53815