Unloading NativeAOT compiled dll?

[Sardelka9515]

Greetings.

NativeAOT has been a fantastic deployment experience.
I can load a natively compiled dll in my C++ app and use GetProcAddress to get the exported function without any problems. However, once I called that function, the dll can no longer be unloaded. Despite successful call to FreeLibrary, the module still remains in the process.
I've tried some hacky approaches, which unfortunately did not work.

Is there any way to unload the NativeAOT compiled dll?

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

Issue Details

---

Greetings.

NativeAOT has been a fantastic deployment experience.
I can load a natively compiled dll in my C++ app and use GetProcAddress to get the exported function without any problems. However, once I called that function, the dll can no longer be unloaded. Despite successful call to FreeLibrary, the module still remains in the process.
I've tried some hacky approaches, which unfortunately did not work.

Is there any way to unload the NativeAOT compiled dll?

Author:	Sardelka9515
Assignees:	-
Labels:	area-NativeAOT-coreclr
Milestone:	-

[filipnavara]

Is there any way to unload the NativeAOT compiled dll?

Unfortunately no. dotnet/corert#7011

[Sardelka9515]

Since I desperately need the functionality in my app, I hooked GetModuleHandleEx with minhook to prevent the module from being pinned. Some memory leaks are tolerable, and I was able to prevent the access violation crash by manually freeing the FLS(by hooking FlsAlloc first). For anyone interested, please see the link in my question above for more details