Skip to content
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

Support for .Net Standard #28

Open
valdisiljuconoks opened this issue Dec 3, 2017 · 8 comments
Open

Support for .Net Standard #28

valdisiljuconoks opened this issue Dec 3, 2017 · 8 comments

Comments

@valdisiljuconoks
Copy link

Any plans in this direction?

@JonasSamuelsson
Copy link

I need to do some xliff file handling from a net core app, is it likely that this will get accepted with an updated nuget package any time soon or should I look for an alternative?

@aldonetti
Copy link

@RyanKing77 - I will try to locate someone in the original team of owners. could you try the same please? thx!

@valdisiljuconoks
Copy link
Author

just give to community and we will make sure it has sustainable future.

@VladimirRybalko
Copy link
Contributor

I've published a new nuget package with .NET standard supporting.
Feel free to use it:
https://www.nuget.org/packages/Xliff.OM.NetStandard

@stiofanmacthomais
Copy link

I've published a new nuget package with .NET standard supporting.
Feel free to use it:
https://www.nuget.org/packages/Xliff.OM.NetStandard

Will try to integrate this today and will keep you posted!

@valdisiljuconoks
Copy link
Author

Haven't checked yet, but is package strongly named?

@VladimirRybalko
Copy link
Contributor

Haven't checked yet, but is package strongly named?

Yes, it's finally strongly named. Feel free to use it: Xliff.OM.NetStandard

@valdisiljuconoks
Copy link
Author

Back in days I just created signed version of the original package :)

https://www.nuget.org/packages/Xliff.OM-Signed/

But thanks for the efforts 👍

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 a pull request may close this issue.

5 participants