Add net6.0 target framework for Bugsnag and Bugsnag.AspNet.Core #179
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.
Goal
Adds a net6.0 target framework for the Bugsnag and Bugsnag.AspNet.Core packages and updates project references accordingly.
Design
Many of the package references (nuget dependencies) for these projects are provided by the .NET platform/framework and only require a nuget package reference when targeting netstandard.
By targeting net6.0 and restricting these package references to the netstandard2.0 target, consuming projects on .NET 6+ will not need to pull in unnecessary nuget dependencies for packages that are provided by the platform/runtime, while projects that still need to use the netstandard2.0 dll can continue to do so.
In addition, I've removed the
DisableImplicitFrameworkReferences
config and removed unnecessary framework references from the project files. This was an outdated approach from the early days of netstandard that is no longer required/recommended for netstandard2.0 (see https://github.com/dotnet/standard/blob/release/2.0.0/docs/faq.md#should-i-reference-the-meta-package-or-should-i-reference-individual-packages).Testing
Tested manually