Skip to content

Conversation

@ti24horas
Copy link

Hi,

Can you please take a look at this PR? I updated the project to support .net core (running on linux).

For what I tested (basic auth, say, play, hangup) it works as the .net 451 version.

I have some questions regarding the "Serializable" classes you have. Is the Serializable used to pass the object through tcp? From my tests, I can see it isn't used in the core library, but for third party consumers, this could be a break change as .NET Core does not support serialization yet.

Well, please take a look and tell me if I can help in anything.

@danbarua
Copy link
Owner

Get in mate! I will take a look at this tomorrow at work.

@ti24horas
Copy link
Author

I didn't understood "This needs to go upstream in https://github.com/damianh/LibLog"

Is the LibLog an external dependency?
The other question is regarding to memory leak problems you mencioned.
I have a valid license of dotmemory and can help you. Just tell me the strategy you have in mind to troubleshoot it.

@gregoriusus
Copy link

Guys, anyone working on porting to net core?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants