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.
A friends mother decided ages ago to get broadband, and signed herself up. Decided on a password she could remember - "pepsi", the name of her daughters first and beloved cat. In those days, most systems didn't check password strength.
Years passed, and she had no problems. The company she was with was bought by TalkTalk and her account transferred fine.
More years passed, until finally he computer died and we had to set up a new one. Well, I had to set up a new one - it gets a little complicated.
Everything went fine, until I had to enter the password for her broadband - and it wouldn't accept it because it was too short, and didn't contain a special character. OK, fine, we'll change it. "Enter existing password". 'p', 'e', 'p', 's', 'i'. "Too short." Oh, fer sake ...
Tech support: "You can't use that, it's too short". "I know: but it wasn't when she set up the account". Took around three hours of back and forthing before they agreed to reset it and email me the new link (since she couldn't get into the account to retrieve anything) ...
I wish she'd used "p*n*s" - at least we'd have got a cheap laugh out of it.
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!
It has been fun, C# 8 has some nice features. Pattern matching switch cleaned up some code (and helps deal with nullability warnings), default interface members (converted to abstract classes), and the biggest one (IMO): nullability warnings. (there is more in C# 8 but I didn't get the chance to test everything).
There were about 200 nullability warnings when I turned that on and some new ones came up while fixing things, it took a while to do something about all of them, but not even that much time. A couple of hours. It found a few real bugs so it was already worth it, and I expect more bugs will be prevented without it having to explicitly fail during testing.
VS2019 does seem slower though. Again. The time from F5 until the program starts running seems longer, compile errors and warnings take longer to show up, switching to a different file sometimes takes noticeable time to process..
when you first start vs2019 it goes on-line to look for style/definition updates and repository updates (git, team..), the vs2019 updater gors on-line to look for package updates, the 4 service workers all go on line to look for updates for their style/template updates. Every 30 minutes they all do it again.
If you are developing with full internet access a huge speed improvement it gained by putting vs2019 behind a firewall (blocking outbound connections - if using repositories just fingrain the allowed connections), it runs as much as 30% faster and no functionality is lost.
...Worried about updates, just open/disable the firewall when you go for lunch.
(don't forget in the about to turn off the "customer improvement" options - it'll still send telemetry back to ms (just a little bit less) - another thing the firewall helps.
Codelens is absolutely worth turning off, it's fine for newbie, it's nothing for anyone else.
- No I'm not one of those worried about being 'spied on,' I just don't appreciate the performance hits on my dev system.
OTOH: personally I'd be quite worried about my abilities if a style analyser is finding bugs.