Skip to content
This repository has been archived by the owner on Apr 3, 2019. It is now read-only.

.NET Core #3

Open
acastaner opened this issue Jun 2, 2016 · 3 comments
Open

.NET Core #3

acastaner opened this issue Jun 2, 2016 · 3 comments

Comments

@acastaner
Copy link

I was wondering if you were planning to port this library to .NET Core?

@ghuntley
Copy link
Owner

ghuntley commented Jun 3, 2016

Up for grabs :)

On Fri, 3 Jun 2016, 12:20 AM Arnaud Castaner [email protected]
wrote:

I was wondering if you were planning to port this library to .NET Core?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#3, or mute the thread
https://github.com/notifications/unsubscribe/AAHxedqUmjEc_U1bnbNX2tX7mdRLufXwks5qHuaygaJpZM4IsmzU
.

anders9ustafsson pushed a commit to nwisesweden/Heijden.Dns that referenced this issue Jun 19, 2018
Begin/End APM methods in class Resolver use AsyncResult class from System.Runtime.Remoting.Messaging namespace. Since .NET Remoting is not available on .NET Standard, these methods are excluded from the .NET Standard project.
@anders9ustafsson
Copy link

anders9ustafsson commented Jun 19, 2018

I have added a project in a separate solution supporting .NET Standard 2.0. Only difference with the .NET Framework 3.5 project is that the .NET Standard project is not able to support the legacy asynchronous methods Begin../End.. in the Resolver class. Hopefully this is not a practical issue since there are already corresponding synchronous methods available.

For details, see PR #9 .

@coder2000
Copy link

You can see my project Ubiety.Dns.Core that supports .NET Standard 2.0

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants