Use AppDomain.CurrentDomain.BaseDirectory to get path of appsettings*.json #375
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.
Description
This fixes #116 by using
AppDomain.CurrentDomain.BaseDirectory
instead ofDirectory.GetCurrentDirectory()
to get the path where an application'sappsettings.json
file(s) should be.Testing
Manually tested an ASP.NET Core 2.2 application hosted in a Windows service. Prior to this fix, this app could not read its New Relic application name setting from
appsettings.json
even though it was there. After the fix, the app is named correctly as expected. I also tested some other cases (.NET 5.0 console application, ASP.NET Core 2.2 and 3.1 apps hosted in IIS in-process) and app naming via appsettings.json worked as expected.Changelog
Will update changelog once I have a PR # for this PR.