| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
@callumnoble @jcarole this PR for .NET Remoting cannot be merged, because more general solution that would work on .NET Core is necessary. .NET Remoting is deprecated and its API is not available in .NET Core and .NET Standard. |
Sorry, something went wrong.
|
@denfromufa Just to confirm, does this mean that Pythonnet 2.0.0 will be the last version that supports .NET Remoting? |
Sorry, something went wrong.
|
For my application which needs this I'm deploying a wheel I built with 2.3 + this patch. Is working well. I see the fails from the CI build. Would you support an #if / #endif conditional for building .NET with version that supports remoting. By definition this check does not need to run on .NET Core since the remoting the library uses wont have been able to run on it! The same define as used here could work? pythonnet/src/runtime/nativecall.cs Line 26 in df2aa64 |
Sorry, something went wrong.
|
@callumnoble that looks reasonable, would you like to make this commit? you can open a new PR if needed. |
Sorry, something went wrong.
|
@denfromufa @callumnoble Exactly. Since .NET Remoting isn't supported by .NET Core (yet, and probably ever), a conditional compilation solution seems ideal. |
Sorry, something went wrong.
|
Will look into doing this sometime in the next few days. |
Sorry, something went wrong.
|
@denfromufa opened new pr for this #637 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
What does this implement/fix? Explain your changes.
#276
Checklist
Check all those that are applicable and complete.