Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

migrate to .net standard 2.0 #646

Closed
wants to merge 2 commits into from

Conversation

tomchavakis
Copy link

support .net core 2.1

@stakx
Copy link
Contributor

stakx commented Jul 19, 2018

Hi @tomchavakis, thanks for the PR.

You might have seen #630. Something like your pull request is definitely planned for the next minor release (4.10.0), but there'll be a patch release first (4.9.1) which is the reason why we cannot merge this into master just yet. Please be patient. ;-)

Also, I am starting to think that it might be preferable to actually target .NET Core 2.x directly, instead of .NET Standard. Please feel free to participate in the discussion over at #630 and update this PR accordingly once we reach a conclusion there.

Copy link
Contributor

@stakx stakx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No changes required just yet, just some thoughts with regard to #630.

@@ -1,7 +1,7 @@
<Project Sdk="Microsoft.NET.Sdk">

<PropertyGroup>
<TargetFrameworks>net45;netstandard1.3</TargetFrameworks>
<TargetFrameworks>net45;netstandard2.0</TargetFrameworks>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We first need to decide which frameworks we want to target before dropping older versions. This will likely need to be changed. I'll give you further feedback once we've figured out things.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be great to support the latest netstandard2.0 version in order to use it at .net core 2.x projects and also the previous versions if it's possible.

@@ -27,6 +27,15 @@
<dependency id="System.Threading.Tasks.Extensions" version="4.3.0" />
<dependency id="System.ValueTuple" version="4.4.0" />
</group>
<group targetFramework=".NETStandard2.0">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we do indeed target netcoreapp2.x instead the dependencies will likely look a bit more minimal. This will likely need to be changed. Stay tuned for more feedback later.

@stakx
Copy link
Contributor

stakx commented Dec 6, 2018

@tomchavakis - Are you still interested in working on this? If so, please confirm briefly by posting here. If not, that's perfectly fine as well.

This PR has been dormant for a while because it wasn't sufficiently clear which platform targets Moq should support in the future. In the meantime, some new information has become available (see e.g. #630 (comment)). My current thinking is that we should probably add net461 and netstandard2.0 targets to Moq. (But I'm not 100% sure I'm reading the .NET cross-platform targeting guide correctly, and that both a net45 and net461 target is necessary. This might warrant some testing.)

Supporting netstandard2.0 would mean that all conditional compilation symbols have to be updated, they will no longer make much sense, nor be named correctly in all instances, in the case of .NET Standard 2.0.

@tomchavakis
Copy link
Author

@stakx Thank's for the detailed comment. I agree with you that net461 and netstandard2.0 should targets to Moq. In case you need any help in some testing for both net45 and net461 I am willing to help.

@stakx
Copy link
Contributor

stakx commented Mar 10, 2019

@tomchavakis, sorry for having disregarded this PR in favour of #784. I actually forgot about your PR until I was already done with mine. 😲

@stakx stakx closed this Mar 10, 2019
@tomchavakis
Copy link
Author

tomchavakis commented Mar 11, 2019

@stakx no worries!!! I am happy that the project updated!!!

@devlooped devlooped locked and limited conversation to collaborators Sep 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants