fix: PublishSingleFile Launch Crash

[MeharDT]

PR Details

Stride applications built for Windows will crash when PublishSingleFile is set to true.

Description

When a Stride application is launched, Assembly.Location is used to find the executable directory and create cache folders. This returns a null value when PublishSingleFile is true. It is instead recommended to use AppContext.BaseDirectory to check for the executable directory.

Additional Info: https://learn.microsoft.com/en-us/dotnet/core/deploying/single-file/warnings/il3000

Related Issue

#2204

Types of changes

• Docs change / refactoring / dependency upgrade
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My change requires a change to the documentation.
• I have added tests to cover my changes.
• All new and existing tests passed.
• I have built and run the editor to try this change out.

[Doprez]

Might be able to also close #1947 with this fix.

[MeharDT]

Might be able to also close #1947 with this fix.

That's a good idea, inline with that the docs should also be updated at some point to include PublishSingleFile instructions.

https://doc.stride3d.net/latest/en/manual/files-and-folders/distribute-a-game.html

[Kryptos-FR]

Is this a correct path if not published as single file?

[MeharDT]

I believe so. My tests included both single file and non single file published builds, all launched without issue.

[Eideren]

Thanks !