- Changed reference to AutoMapper to the range [11.0, 12.0)
#12
Conversation
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
As a breaking change from version `11` onwards is dropped support for `net461` it seems unreasonable to keep support for this framework in the extension also. - Switched targets to only support `netstandard2.1` This is due to the fact that AutoMapper from version `11` has dropped support for `net461` target. Also removed optional dependencies, as package only target single framework now. - Switched targets for test project to `net6.0` Mainly because AutoMapper `11` targets `netstandard2.1` and this is not supported in `netcoreapp2.1`, also this target framework is no longer supported generally so updating seems like a good idea. Secondly I work on an Apple Silicon machine, so bumping to something compatible with .Net 6 was required for me to be able to run the tests. - Updated using statements to target `AutoMapper.Internal` when necessary - Use new `.Internal()` rather than old `.Advanced`
|
To fix the build you'll need to add this step to pull in .NET 6: |
Sorry, I'm an idiot forgot to include with |
…to mda/upgrade-to-AutoMapper-11
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As a breaking change from version
11onwards is dropped support fornet461it seems unreasonable to keep support for this framework in the extension also.netstandard2.1This is due to the fact that AutoMapper from version
11has dropped support fornet461target.Also removed optional dependencies, as package only target single framework now.
net6.0Mainly because AutoMapper
11targetsnetstandard2.1and this is not supported innetcoreapp2.1, also this target framework is no longer supported generally so updating seems like a good idea.Secondly I work on an Apple Silicon machine, so bumping to something compatible with .Net 6 was required for me to be able to run the tests.
AutoMapper.Internalwhen necessary.Internal()rather than old.Advanced