I was following the new .NET Core 2.2 –> 3.0 upgrade document, but when I updated my unit test project files, I accidentally set the SDK to Microsoft.NET.Sdk.Web because that’s what my ASP.NET Core 3.0 web project was. via GIPHY The unit tests still ran and worked… for the most part. One of them failed, … [Read more…]
So I was writing an inline if statement the other day… you know the ones – booleanStatement ? resultIfTrue : resultIfFalse; It was pretty simple, so I didn’t think too much about it until I ran some unit tests…. via GIPHY Here’s what my code kind of looked like: So, what would you expect the … [Read more…]
Sometimes you just need some logging to do a sanity check that things are actually working the way that you’re expecting. via GIPHY Here’s how to turn logging on in ASP.NET Core 2 for SignalR: I’ve had to look this up more than twice, and its not exactly easy to find in the Microsoft docs, … [Read more…]
Sometimes, especially when you’re debugging or planning out your component layouts, it can be useful to just write out the entire object as JSON so you can see just what you’re dealing with. You can do this in Chrome’s console usually with good results, but sometimes it would be easier to see it in the … [Read more…]
Recently I had a problem where in an Angular unit test where I had an object that was being initialized in ngOnInit from a service. As far as I could tell, everything should be working, but the test would fail because I was trying to set a property on the object before it had finished … [Read more…]
How many times have you wanted to check the IIS Request Logs to see if anything is going wrong, only to find a bunch of arbitrarily named W3SVx folders because you have more than one website running? And then you open the folder, but all of the log files are also arbitrarily named? And then … [Read more…]