-
Notifications
You must be signed in to change notification settings - Fork 747
Added side-by-side VS 2017 build with NetStandard 1.5 support. #444
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
Conversation
Unable to parse mention-bot custom configuration file due to a syntax error.
Error message:
|
@dmitriyse, thanks for your PR! By analyzing the history of the files in this pull request, we identified @vmuriart, @tonyroberts and @tiran to be potential reviewers. |
I will inject ReflectionBridge right into PythonNet, to save single-Dll deployments. |
Codecov Report
@@ Coverage Diff @@
## master #444 +/- ##
===========================================
- Coverage 77.03% 66.56% -10.48%
===========================================
Files 62 63 +1
Lines 5526 5270 -256
Branches 886 843 -43
===========================================
- Hits 4257 3508 -749
- Misses 981 1506 +525
+ Partials 288 256 -32
Continue to review full report at Codecov.
|
7ec0c02
to
563a844
Compare
Alot of your changes are also changing the encoding of the files. |
@vmuriart did you have a chance to review this .net core integration? |
Very much against it in the current form.
A better path would be to either refactor some more or completely move to it. |
@dmitriyse @vmuriart We can't move completely to .NET Core, it doesn't support DllExport and
demo apps will break. So .NET Framework should still be tested.
…On Mon, Apr 24, 2017, 10:21 AM Victor Uriarte ***@***.***> wrote:
Very much against it in the current form.
- Adds too many build directives, making the code complicated. We just
removed a bunch of them for PY2/PY3, don't want to readd them now for this
- No new CI added for .net core. If something is added and breaks we
won't know.
A better path would be to either refactor some more or completely move to
it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#444 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHgZ5fH4IyM3-bqj37qORAhslOt1VA7bks5rzL4BgaJpZM4Mr81i>
.
|
Public constants replaced to static readonly fields. Relaxed platform binding.
@dmitriyse can we close this pull request, or is this still part of other pull requests for .NET Core support? |
Yes, we can definitely close this PR. It's outdated. We will not support .NetStandard lower than 2.0. |
What does this implement/fix? Explain your changes.
Added new files that allows to build PythonNet targeting NetStarndard 1.5
Current build scripts are not affected.
All code modification should be loss-less for current build configurations.
New VS 2017 build files are capable to build net40 and NetStandard 1.5 assemblies.
This change is a first CoreCLR compilable version. Probably it is not functional yet.
The work is in progress.
Also CoreCLR assembly/package now have 3.0.0-alpha version. Probably it's ok, if PythonNet with CoreCLR support is scheduled to 3.0.0
...
Does this close any currently open issues?
Not closes yet but relates to #96
...
Any other comments?
We can join this branch into the master even now, and continue to develop with the additional target (NetStandard 1.5).
But it is reasonable to do it after the point where both Windows and Linux configurations will be tested.
...
Checklist
Check all those that are applicable and complete.
AUTHORS
CHANGELOG