You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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.
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!
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!
The text was updated successfully, but these errors were encountered: