-
Notifications
You must be signed in to change notification settings - Fork 13
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
Port to .net core... #9
Comments
Honestly, I don't have any experience in .NET Core. I am back in den good old Java world for several years now, but I will try to figure it out when there is time. So please be patient ;-) |
Hi, Which target framework are you using? I've created a net5.0 branch. Can you check it out? Thx |
I think it would be the best to target .netstandard, as it will be compatible with .net framework and .net core as well. My proposal is to not to be bound to my own project, but just to be generic component, available to multiple end-users who wants to use it. |
See also: https://github.com/tapika/swupd/blob/master/docs/testing.md#mocking-and-verifying-log LoggedMock.cs / LoggedMockInterceptor.cs - logged mock is probably the place where I could connect whole thing. |
I decided to target net40 and netcoreapp3.1 and the tests are running with net48 and net6.0. Is it possible for you to just build NProxy by your own and test it within your project? I've renamed the branch to cross-platform. |
I haven't published the NuGet package yet but one is available on AppVeyor. |
I know there was once upon a time following ticket:
#8
but it was closed long time ago.
Meanwhile - I would like to use logging + testing for testing, and I would prefer to use fastest proxy generator + fastest call dispatcher.
Would it be still possible to port NProxy to .net core ?
The text was updated successfully, but these errors were encountered: