Fix Crash due to GetExecutingAssembly Location returns empty string

[SaNeOr]

In .NET 5 and later versions, for bundled assemblies, the value returned is an empty string and the first parameter of Path.Combine cannot be empty.

https://learn.microsoft.com/en-us/dotnet/api/system.reflection.assembly.location?view=net-5.0#System_Reflection_Assembly_Location

It is enough to use AppContext.BaseDirectory.

[lyra95]

Is this fix going to be merged in next release? @skardile-perforce

[skardile-perforce]

In .NET 5 and later versions, for bundled assemblies, the value returned is an empty string and the first parameter of Path.Combine cannot be empty.

https://learn.microsoft.com/en-us/dotnet/api/system.reflection.assembly.location?view=net-5.0#System_Reflection_Assembly_Location

It is enough to use AppContext.BaseDirectory.

Thanks @SaNeOr for the change.
@lyra95, Yes the team will look into this to accommodate it into next release.

[kalulas]

Encountered the same issue with my single-file build application. It would be greatly appreciated if this issue could be fixed in the next release.

[edemartel]

Since .NET 6, you can also use Environment.ProcessPath to get the path to the executable.