Replace Assembly.Location to AppContext.BaseDirectory

[sappho192]

Pull request type

• [ ] Update
• [x] Bugfix
• [ ] Feature
• [ ] Code style update (formatting, renaming)
• [ ] Refactoring (no functional changes, no api changes)
• [ ] Build related changes
• [ ] Documentation content changes

What is the current behavior?

When you Publish the app which is based on one of the templates (Blank/Compact/Fluent), the app will be crashed since Assembly.GetEntryAssembly()!.Location in App.xaml.cs:23 will always return null. https://github.com/lepoco/wpfui/blob/09eeabd684f2e8f242ceff6deb60e1546d2a7bbf/src/Wpf.Ui.Extension.Template.Blank/App.xaml.cs#L23

This doesn't happen if you "build" the app (both Debug or Release), but when you "publish" it.

This issue also can be notified in build message when you publish the app: IL3000: 'System.Reflection.Assembly.Location' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.

Issue Number: N/A

What is the new behavior?

• The app will be properly published and executed

Other information

Actually the demo app Wpf.Ui.Demo.Mvvm already solved this issue like below, so this can be also applied to the template projects. https://github.com/lepoco/wpfui/blob/09eeabd684f2e8f242ceff6deb60e1546d2a7bbf/src/Wpf.Ui.Demo.Mvvm/App.xaml.cs#L30

References:

• https://learn.microsoft.com/en-us/dotnet/core/deploying/single-file/warnings/il3000
• https://learn.microsoft.com/en-us/dotnet/core/deploying/single-file/overview?tabs=cli#api-incompatibility
• https://github.com/dotnet/corert/issues/5467