Vitek Karas

> The default way that applications parts are found is using IHostingEnvironment.ApplicationName and this defaults to Assembly.GetEntryAssembly().Name which might be the expected name in this case. @davidfowl Would it make...

Seems like all the questions have been answered. So closing this.

I created https://github.com/dotnet/aspnetcore/issues/43460 to track this on the aspnetcore side.

How did you build the test in question for NativeAOT? I tried the usual way but it fails for me.

Having a GUI and Console version of the app in the same exe seems to be pretty tricky on Windows. Search for example for "windows GUI app with console" there...

This would mean that you're running the CLI (command line) version as a child process. Which may be fine in your scenario (it's frequently not desirable though). You could probably...

@sbomer is looking into this

Once the "linker can't run" problem is fixed, there will be additional failures caused by fixes in the linker (runtime has wrong/missing suppression in some places). @jkurdek is working fixing...

/azp run runtime-wasm-perf

/azp run runtime-wasm-perf