-
Notifications
You must be signed in to change notification settings - Fork 11
Port to NETStandard #40
Comments
Need latest libgit2sharp nuget package (with supports for netstandard1.3) to be released. |
I have started work in a branch but it's not yet successfully building.
Following cannot be resolved:
|
Have attached an API portability analysis: ApiPortAnalysis.xlsx |
@dazinator |
Yeah the serialisation constructor for exceptions used to be a best practice. Im not sure its required anymore though.. |
I would add a compiler directive for these ReSharper features based on the platform you are currently viewing in the editor, so at least if they switch to the full .NET Framework, these features will still work for them. (ie. #if NET45)
Since binary serialization is not supported until .NET Standard 2.0, I have been using compiler directives to comment this feature out |
Happy to just remove all blockers, rather than solving |
Removed SerializationInfo and updated to newer version of JetBrain.Annotations here. I was unable to push my commits to GitTools.Core@feature/netstandard. Edit: So it seems that all thats left now is waiting for LibGit2Sharp to release a nuget with netstandard support. |
@pdrhsm As a workaround for LibGit2Sharp not having a Portable library... to continue working, in my GitTools.Testing PR, I modified the csproj to conditionally include the portable library version depending on the TargetFramework. GitTools.Testing.Tests.csproj#L32-L40 Also, you should open a PR against feature/netstandard if you want to merge your changes in. |
Now that GitTools.Core is targeting netstandard1.3 - The |
The next blockers are all with The sole usage for the |
Ok I think this can be reviewed now. I ended up removing |
PR Submitted. |
Waiting on GitTools/GitTools.Testing#6 to be merged, so can then get the tests on travis to run under netcoreapp. |
@dazinator as far as I can see this seems to be done? If so; when can we expect as release?! 👍 |
@pdrhsm - |
Feature description
Port the solution NETStandard.
This will unlock ability to port GitVersionTask to .NETStandard.
This will unlock dotnet cli builds for projects that consume GitVersionTask
Here is the API Portability analysis: ApiPortAnalysis.xlsx
The text was updated successfully, but these errors were encountered: