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

Consider releasing RuntimeInformation methods as standalone package #1078

Closed
ob-stripe opened this issue Feb 22, 2019 · 2 comments
Closed

Consider releasing RuntimeInformation methods as standalone package #1078

ob-stripe opened this issue Feb 22, 2019 · 2 comments
Assignees

Comments

@ob-stripe
Copy link

Hi,

Retrieving the correct version information for the .NET runtime is notoriously difficult. This project appears to have mostly solved this problem via the methods in RuntimeInformation.cs and some other utility methods.

Would you consider releasing this as a separate library? I think it would be tremendously useful for library developers. For instance, Stripe maintains a .NET library and gathering proper metrics about runtime versions has always proven difficult.

Thank you for your consideration!

@adamsitnik
Copy link
Member

Hi @ob-stripe

I am sorry, but no. It would add complexity on our side without any gains for us. The code is MIT so you can just copy-paste it.

If you believe that similar API should be exposed by the .NET Core base class library itself please create an issue in https://github.com/dotnet/corefx/ and tag me and I will ping the right people on the Team to discuss it.

It's also a duplicate of #1017

@ob-stripe
Copy link
Author

Sorry for the dupe, I did try to check if this had been requested before but obviously didn't look hard enough.

It would definitely be nice if .NET Core did make it easier to retrieve the runtime version and I might follow your suggestion, although it would only solve half the problem for libraries that also support .NET Framework.

We'll probably just go with copying the code for now. Thanks for the reply!

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

No branches or pull requests

2 participants