The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I went through much of this headache last week. Following an update, the wife's all-in-one kept failing to boot, instead blue-screening with a 'machine check exception'. After 3 attempts at restoring all failed, I decided that it needed a fresh OS and if I was going to go through that trouble, I might as well put it on a new SSD...and since the guts were going to be exposed, I should go ahead an double the memory to a respectable 8GB. It was probably silly to do this, but in order to make it as easy as possible, I purchased Win 10 Home on a USB stick.
I get all the parts in, get Win 10 installing, and all seems good...until it started setting up devices then blue-screened. It took me awhile to figure it out, but the problem was the onboard wifi adapter. I had to fight with it to remove it, but afterward Win 10 finished the install and the computer is better than new, going from over 2 minutes to less than 10 seconds from boot to Google.
Two things that I'd like to note here:
0: I'm surprised that a lowly non-critical device such as a wifi adapter can stop Win 10 from loading or finishing an install. Why not just disable the sucker and move on?
1: The error message was totally useless...OK, hardware issue...you know which device caused the crash, so why not be a little more helpful and share!
One more thing that has come to mind is that a great way to boost new PC sales would be to make older hardware obsolete. I had just about given up on the PC discussed above. Two weeks ago, my sister-in-law asked about an issue where WU keeps freezing at 82%...first question, 'how old is it'. answer, > 6 years, so I took the easy way out and advised to get a new one. I've since talked to my brother and he's going to try a new SSD and a fresh Win 7 install.
I have a Pi with camera. Works fine streaming to FF or Chrome. So, I says to myself, what about Edge? Puts in the IP and port 8081 and it says "what do you want to do?". I says "open says me". Well, open. It says it can't download it. What am I doing wrong? I know, clicking on the Edge icon.
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
So I decided to upgrade a .NET Core 2.1 project to a .NET Core 2.2 project, after all what harm can it do?
A LOT APPARENTLY!
First, the build breaks.
Read some Scott Hanselman blog and I need to use the .NET Core Tool Installer in my build to install the .NET Core 2.2.100 SDK.
Done and on to Azure!
Except the site went down...
Turn on all logging I can find, but nothing!
I turn on detailed information in the browser in the web config, because I had absolutely nothing to go on (at this point the whole world can read my errors).
And there it is, a nice error "Handler "aspNetCore" has a bad module "AspNetCoreModuleV2" in its module list"
Do some additional reading and I can't make any sense of it.
Decide to try a completely new ASP.NET Core 2.2 project and immediately release it to Azure, same error.
WTF MICROSOFT IF EVEN YOUR DEFAULT TEMPLATE DOESN'T WORK HOW AM I SUPPOSED TO MAKE IT WORK!?
I made the only fix I could find... Revert to .NET Core 2.1...
(I just found out the "old" handler is AspNetCoreModule, perhaps it would've worked if I used that with 2.2?)
That's working to throw your work down the drain
Usually, I wouldn't mind all that much, except I wanted to go to bed about an hour ago
At least the site is up and running again
MS is putting out a lot of rubbish lately. I was trying to get my feet wet in UWP yesterday. The default Class library and Application projects wouldn't even compile properly at first. It would give me the most obscure compilation errors and send me off to a googling spree. Had to turn off Native compilation, randomly updated some nuget references, did some random nuget restore commands, and finally got these very basic projects compiling. I'm seriously starting considering jumping ship.
Last Visit: 15-Dec-18 21:59 Last Update: 15-Dec-18 21:59