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.
1. The lounge is for the CodeProject community to discuss things of interest to the community, and as a place for the whole community to participate. It is, first and foremost, a respectful meeting and discussion area for those wishing to discuss the life of a Software developer.
The #1 rule is: Be respectful of others, of the site, and of the community as a whole.
2. Technical discussions are welcome, but if you need specific programming question answered please use Quick Answers[^], or to discussion your programming problem in depth use the programming forums[^]. We encourage technical discussion, but this is a general discussion forum, not a programming Q&A forum. Posts will be moved or deleted if they fit better elsewhere.
4. No politics (including enviro-politics[^]), no sex, no religion. This is a community for software development. There are plenty of other sites that are far more appropriate for these discussions.
5. Nothing Not Safe For Work, nothing you would not want your wife/husband, your girlfriend/boyfriend, your mother or your kid sister seeing on your screen.
6. Any personal attacks, any spam, any advertising, any trolling, or any abuse of the rules will result in your account being removed.
7. Not everyone's first language is English. Be understanding.
Please respect the community and respect each other. We are of many cultures so remember that. Don't assume others understand you are joking, don't belittle anyone for taking offense or being thin skinned.
We are a community for software developers. Leave the egos at the door.
To be fair, it's a minority of my systems that run into these sorts of problems.
OTOH, it's still a little disconcerting when my Server 2019 VM started exhibiting update problems so soon after that was still a recent, full, and clean install...running on their own hypervisor, so the physical hardware is abstracted away...
I'm not aware of any "large font" problem. That's a user choice.
I have a 4K display, and refuse to rescale the UI "because I have the pixels to spare". No, I want to run it at its native resolution, otherwise I'm just wasting screen real-estate (using up to twice as many pixels to render the same amount of data). Across 40", the text is actually smaller than it is on the 27" 1080p monitor I have sitting next to it.
Or are you talking about something else altogether?
I have weak eyes and with those high resolution monitors the normal font size is way too small... So I use 125%...
And if you Google for Windows 10 DPI you will see what I have here...
One of the fascinating things, that if I create a brand new WinForm application (using latest VS2019) it looks perfect in the designer (assuming I have configured VS compatibility mode correctly) but blurred when running... So I either have to set the exe's compatibility or change the form's properties in VS...
An other one is that IIS manager seems to be immune to any configuration I threw at it...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
I've had a Windows Server 2019 VM refuse to install updates for quite a while now. Since today's patch Tuesday, figured I'd try to dig a little more into it since I'm going to be looking at that machine again sooner or later.
MS has made it clear for a while now that, with Cumulative Updates, you can take a brand new OS install, and immediately bring everything up to date just by installing the latest available Cumulative Update. Since this particular VM refuses to install the latest CU for Server 2019 (KB4522355, which came out October 24th) directly from my WSUS server, I figured I'd download the offline installer, and run that locally (more often than not this solves this type of problem).
Nope, "this update is not applicable to your computer". Tried many things, no change.
On a hunch, I tracked down the CU prior to that one--from October 8th (KB4519338). That one didn't complain, and is now in the process of being installed (as I'm writing this).
If these CUs are truly "cumulative", why does the newer one insist it's not applicable...? Windows Update itself insisted I needed it...
Does anyone else find it to be a pita to get pestered by the annoying system modal 'Updates are Available' screen where the only option is to 'View Available Updates'! Where is my 'Ignore Again' option?