NativeAOT Libraries support for DllImportSearchPath.AssemblyDirectory is undefined

[AaronRobinsonMSFT]

In #90120 support was added for NativeAOT applications to respect DllImportSearchPath.AssemblyDirectory as relative to the binary on disk. However, this doesn't necessarily apply to NativeAOT scenarios for libraries.

• What should the assembly directory be when a class library is NativeAOT'd?

See original application issue at #89874.

[ghost]

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

Issue Details

---

In #90120 support was added for NativeAOT applications to respect DllImportSearchPath.AssemblyDirectory as relative to the binary on disk. However, this doesn't necessarily apply to NativeAOT scenarios for libraries.

• What should the assembly directory be when a class library is NativeAOT'd?

See original application issue at #89874.

Author:	AaronRobinsonMSFT
Assignees:	-
Labels:	area-NativeAOT-coreclr
Milestone:	Future

[AaronRobinsonMSFT]

/cc @elinor-fung

[jkotas]

The underlaying problem is that AppContext.BaseDirectory is defined as Environment.ProcessPath directory:

runtime/src/libraries/System.Private.CoreLib/src/System/AppContext.AnyOS.cs

Line 22 in 40b39ff

string? path = Environment.ProcessPath;

It does not necessarily work well for AOT compiler libraries if they are in different directory than the process itself.