8thString

Visual Studio 2022 not running unit tests I have projects with unit tests working properly using Visual Studio 2019. Installed Visual Studio 2022 on another machine to try it out, running Nunit unit tests does nothing. It does not say it failed nor indicate something is wrong. It was actuallying failing but I am not looking at the correct output log. As you observe from the above screen capture, the default log shows Build output. What you wanted is the log for Tests . See below for the correct view. The Tests output shows the issue front and center. The tests were failing because it was configured to use .Net Core 3.1.x but it was not avaiable on the machine. One way to fix it is to use Visual Studio Installer and select .NET Core 3.1 Runtime (LTS) .

How to properly delete Windows10Upgrade folder So you are running out of storage and you are staring at Windows10Upgrade and wondering how you can get rid of it correctly? Well, fear no more, it is easy. Open up Control Panel and navigate to Control Panel\All Control Panel Items\Programs and Features or appwiz.cpl . Then look for Windows 10 Upgrade Assistant and uninstall the application.See below for how it looks like.

Get hostname from an IP in Windows Method 1 - Using built-in ping. This only works if a working DNS server has reverse look-up configured. c:\>ping -a 8.8.8.8 The hostname for 8.8.8.8 was returned as dns.google , below shows the output details. Pinging dns.google [8.8.8.8] with 32 bytes of data: Reply from 8.8.8.8: bytes=32 time=52ms TTL=112 Reply from 8.8.8.8: bytes=32 time=56ms TTL=112 Reply from 8.8.8.8: bytes=32 time=59ms TTL=112 Reply from 8.8.8.8: bytes=32 time=56ms TTL=112 Ping statistics for 8.8.8.8: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 52ms, Maximum = 59ms, Average = 55ms Method 2 - Using nslookup c:\>nslookup 8.8.8.8 This is the same as method 1, it needs a working DNS to provide the information Server: somedc.com Address: some_ip_here Name: dns.google Address: 8.8.8.8 Method 3 - Using nbtstat c:\>nbtstat -a 192.168.1.101 With the added bonus that