Technology is moving at the speed of light, .NET upgrades are huge, and new features are plentiful. I find that many development teams struggle with the most basic upgrades from a time perspective. Most commonly, I see teams get the upgrade done to a point of "it builds," and they move on. In many cases, this works, but long-term it will often bite you. There are many situations where a .NET upgrade is a "You should really do this" type recommendation that, in future editions, will become "You must do this." So, trying to spark the balance of upgrading to working and upgrading to be fully proper can be hard to balance.
In my most recent episode of the Tech Vault with Mitchel Sellers, I dive into a few quick things that you can do to help make that process easier!
I hope the information above was helpful! If you have any ideas for future blog psots, or videos please don't hesitate to reach out!