The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
At any rate I was pleasantly surprised when they said the .NET Core 3 rc2 installer (or rc3? or some other number!) and forward will uninstall previous (pre-release) versions, when installed.
And I checked it, it was true!
I'd like to bounce some code-in-the-grammar ideas off of you at some point. I have an idea that may allow for associated code without it having to be in the grammar, using attributes and a "codebehind" class but i'd like a 2nd opinion. Just whenever.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
Unless dealing with faulty hardware or bad drivers, it's literally been years I've seen a BSOD that the OS could be blamed for. Dare I say, these days I don't see Windows outright crashing/freezing any more frequently than some Linux distributions...
+1 to the no BSOD club here. I haven't had any at all in Win10, and I code in VS2019 Pro (Knocking on some serious wood here). 2 years ago, I did have a workstation class motherboard die on me. Likely was around then was the last time I've seen a BSOD in Win7. Drivers can cause this as well. But I tend to buy quality hardware that seldom suffer those issues.
Two of my users regularly still get BSODs.
I do know exactly why though for these two machines.
Whenever M$ update their handling of graphic devices, the vendor provided drivers for the graphic devices on these two (out of 20 odd physical machines) shut down and bang BSOD.
Of course, what we see on the screen gives absolutely no clue that this is the reason, just learnt the hard way.
Management asked me if we could invoice M$ for the several hundred hours of research I had to do to find the issue and document it sufficiently that someone else can recover these machines if I am not on-site. I suggested that this would only cause amusement in the the house of small soft things.
I didn't much like Win 10 when it came out: compared to Win 7 it was ugly, dull, and schizophrenic.
And yes, it still is all of those things.
But ... it doesn't crash on me, or anyone I support - no BSOD, no nothing. Some apps do, from time to time but that's not the OS's fault.
In all, it works. And when it runs on hardware that is designed to support it (like the Surface) it runs very well indeed. considering the number of different hardware combinations it has to work with, it's a small miracle that it ever manages to boot up, much less actually run!
Sorry - but in my experience, it's pretty reliable these days. Even if updates can be a PITA.
Sent from my Amstrad PC 1640 Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
The only issue I faced on my latest machine was the mouse would do this weird stuttering and hang up for a second, appeared t happen randomly. I don't know how many sites and pages I looked at trying to get to the bottom of it. I even though for a while it was certain areas on the mouse pad and the optic sensor etc. etc.
In the end, I removed the Logitech Unify USB dongle and paired the mouse (Logitech MX Master 2S) via bluetooth instead and the problem appears to have now gone away.
Just for info: I had a similar problem with a unify dongle - so much so that the keyboard would freeze too. Moving to a bluetooth mouse fixed the problem.
Having done a lot of reading and then experimenting, it turns out that the dongle's communication can be disrupted by WiFi signals and other Rf emissions. I relocated the dongle from the PC under the desk to a USB 3 hub that sits nearer to the keyboard and mouse than any other device that uses radio etc, and now it works fine.
Once upon a time, support.microsoft.com was a technical support site worth it's weight in gold (it really worked, just input the error message and you got the right answer 99% of the time).
Then microsoft decided that everything had to be powered by Bing...
So now it's completely dysfunctional, and aimed at users instead of tech support.
Back in the days while I was at Intel, we used to debug BSODs to figure out what was going on. Now, I was no expert in it at all, but mate who used to sit right behind me was a full-timer on this front. Most of these BSODs were either caused by a product that we sold (and therefore we were trying to resolve the issue), or was to prove to someone (like a laptop manufacturer) that it wasn't our product that was causing the BSOD.
Having said that, I've not seen a BSOD in a very very long time. On the odd occasion where I witnessed one, Windows core dumped gracefully and restarted like nothing happened.
Last Visit: 31-Dec-99 18:00 Last Update: 25-Jul-21 15:31