Fixed app published as singleFile not running (issue #483)#506
Merged
pomianowski merged 1 commit intolepoco:developmentfrom Jan 23, 2023
Aybex:development
Merged
Fixed app published as singleFile not running (issue #483)#506pomianowski merged 1 commit intolepoco:developmentfrom Aybex:development
pomianowski merged 1 commit intolepoco:developmentfrom
Aybex:development
Conversation
pomianowski
approved these changes
Jan 23, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently executables published as singleFile are not running. (See Issue #483)
The problem is in setting the Host object's Base Path as "Assembly.GetEntryAssembly()!.Location" returns null.
Based @MrCosmo suggestion changing it to "AppContext.BaseDirectory" works perfectly.
Pull request type
Please check the type of change your PR introduces:
What is the current behavior?
Issue Number: #483
What is the new behavior?