Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Runtime.Current.Version null on Windows 10 2004 .NET Framework 4.8
See original GitHub issueRuntime.Current.Version is null on .NET Framework 4.8 after upgrading to Windows 10 2004, build 19041.264.
I expected it to be “4.8”.
Also, to avoid this becoming null again later, I suggest making Version the largest version where the build number is not too large. Showing e.g. 4.8 on a 4.8.1 installation is much better than getting a null.
Cheers, Kristian
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (8 by maintainers)
Top Results From Across the Web
Runtime changes for migration to .NET Framework 4.8.x
MemberName property returns null . In .NET Framework 4.8 version prior to the October 2019 update, it returns the member name.
Read more >.NET Framework 4.8 is available on Windows Update ...
NET Framework 4.8 is available for the following client and server platforms: Windows Client versions: Windows 10 version 1903, Windows 10 ...
Read more >KB4486153 Gives error 0x80092004 trying to update/fix . ...
net is broken on my computer. When I try to start Powershell, I get Internal Windows PowerShell error. Loading managed Windows PowerShell ...
Read more >June 8, 2021-KB4601554 Cumulative Update for .NET ...
Addresses an issue where the entire process would be torn down when a NullReferenceException propagated out of an exception filter.
Read more >Cannot install .net framework 4.8 (KB4486153) on ...
Cannot install .net framework 4.8 (KB4486153) on windows 10 LTSC ... [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] originated in ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It was actually missing two values.
Thanks for raising this. The SDK will report the right value from the next release. Sentry will report also 4.8 even for apps on old SDK version once we release my patch on Relay
Is it the case Sentry’s receiving raw description and not handling it?
This seems to be an issue but at least can be fixed on the server.
The handling is done here:
https://github.com/getsentry/relay/blob/8a226679c5d7023df00a71da293fec798f0f248f/relay-general/src/store/normalize/contexts.rs#L21-L68
But it seems the SDK needs to send
buildalong.