-
-
Notifications
You must be signed in to change notification settings - Fork 74
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
dotnet core compatibility #1
Comments
Hi Nico, Currently I'm not planning to port the library to .NET Core. At now there are not so much users of the DryWetMIDI to proceed with .NET Core compatibility. This task can take some time but currently I'm focused on new features of the library. But maybe in the future I'll come back to your issue :) Anyway thank you for your interest to the DryWetMIDI! Feel free to open new issues and ask any questions about the library. Max |
Hi Max, |
Hi Nico, It is because the Thank you for your feedback and for remebering me about non-ASCII encodings in text-based meta events. I'll try to provide a solution in the next release which should be at the beginning of August. Max |
Thanks Max, I will await the update. |
Nico, I've created separate issue for the non-ASCII encodings support (#2) and moved all our discussion about this problem to the first post of the new issue. All comments on this bug should be placed there. Please press the Subscribe button there to make sure you will recieve all notifications about the issue. This issue for discussion about .NET Core support only. One problem – one issue. Otherwise it will be difficult for me to maintain list of issues and link commits to specific ones :) Max |
DryWetMIDI 1.2.0 has been released. This release contains a fix for the #2. |
I see I never replied, sorry about that. Thanks Max and a happy new year. |
Hi!
Any plans for making this library dotnet core-compatible?
Kind regards,
Nico Witteman
The text was updated successfully, but these errors were encountered: