-
Notifications
You must be signed in to change notification settings - Fork 17
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
Is it .NET Core ready? #94
Comments
It's not currently available for .NET Core, but I'm open to it 😄 |
I'm really looking forward to it! Thanks for the quick response, Master Mark! |
It seems that this is not possible right now. Albedo references code in the System.Reflection and System.Type namespaces which has not been ported to .Net Standard 1.6 or .Net Core 1.1. I have analyzed the Albedo DLL using the .Net Portability Analyzer. I have attached the result which tells us that the required changes will be done in .Net Standard 2.0 and .Net Core 2.0. |
It's already implemented in master. We target .NET Standard 2.0 as it contains all the API we need. |
Good news everyone! 🎉🌟🎆 I've just published v2 that supports .NET Standard 2.0. Be aware of the announcement in ReadMe. CC @AlbedoOrg/core |
Great job, @zvirja. |
My project (OmniXAML https://github.com/SuperJMN/OmniXAML/) does make use of reflection quite intensively, so I thought about using this library. The problem is that right now I'm porting it to .NET Core.
Is Albedo usable by .NET Core libraries using .NET Standard?
The text was updated successfully, but these errors were encountered: