Targeting netstandard2.0, net45, net40#64
Conversation
|
Nice! What's stopping you targeting a lower version of the .NET Standard out of interest? |
|
Naivety probably! :-) What do you recommend? The main issue preventing us porting before now was AutoFixture not having been ported so netstandard2.0 helped with that. |
|
AutoFixture not supporting .NET Standard has been a thorn in the side of a few projects. Luckily it looks like the port has almost been completed, and judging by the pull request it looks like it'll target .NET Standard 1.5, so there's scope to drop the target down to 1.5 once it's eventually released, in the meantime netstandard 2.0 is the next best thing. |
|
Looks like AutoFixture .NET Core changes have been merged and ready for release in v4 which is good news. |
|
Sweet!
…--
Rob Moore | Readify Principal Consultant, Technical Specialist (Microsoft Azure) | m +61 400 777 763 | e rob.moore@readify.net | w readify.net
On 13 Sep 2017, at 7:29 am, Joseph Woodward ***@***.***> wrote:
Looks like AutoFixture .NET Core changes have been merged and ready for release in v4 which is good news.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Good to know, thanks! |
|
Probably worth merging this then targeting lower .NET Standard versions in a separate pull request. |
|
Any idea when we can get this merged (I see AutoFixture 4 RC1 has now been released) |
|
AutoFixture v4 is now stable. Whats missing in this PR to get merged, @mwhelan? Due to namespace changes in AutoFixture v4, its hard to consume this package together with latest version of AutoFixture. Happy to help to with any outstanding work. |
4 participants
First cut at netstandard2.0 support. with multi-targeting for .Net 4.5 and .Net 4.0 also
Everything compiles and all the tests pass.