Entries for 2019

March 22, 2019

Monitoring and Improving Code Quality

Regularly I'll be asked which tools/utilities I like to help improve my code quality, or to solve specific issues. Recently I've been working to improve the code quality, unit test coverage, and other aspects of many projects, some mine, and some Open Source. Maintenance of code is always a sticky situation, its important to the long term support, however, when working with clients if they cannot see it, it is hard for them to justify the costs. To help get around this limitation I've been using a product called NDepend for a number of years, but only internally. This has all changed, and I thought what a great time to share my experience.

March 22, 2019

Avoiding DNN Upgrade/Install Errors on Azure

We have been using Microsoft Azure for a number of years to host this website, our company website, and countless customer websites. As DNN Platform has grown, we have recently encountered a few errors that have impacted our installations & upgrades that might be worth considering if you are attempting an upgrade of a DNN Platform or EVOQ installation on Windows Azure.

January 25, 2019

Quickly Redirecting Old URL's with .NET Core

I recently deployed a big new .NET Core website to replace an existing ASP.NET based website. This new site has been optimized for performance, stability, and SEO value. As such, the URL structures for major sections of the website had changed. Many of page URL's were not majorly concerning as the search engines would easily pick up the new URL's in a matter of a few days. However, the old blog URL's that were shared publicly on many external channels became a big concern. I'll dive into how I solved this in a manner that works, quickly, easily and without major impacts to performance etc.

January 12, 2019

Bridging the Gap: Ease of Use & Enterprise Practices

Often times in the software development world we are constantly working towards the "best compromise" solution for our customers or employers. In many cases, there isn't one "right" way to do things. Each application will have its own requirements for testability, durability, and longevity. With differences in these requirements, the methods used for development or the need to engineer long-term support situations will vary. To this point, we often find in the .NET Framework that certain methods, API's and processes are more geared towards the "easy to use" solution, rather than the "enterprise" solution. In this post, I dive into this concept/problem a bit, and introduce a workaround that I have been working on.

Content provided in this blog is provided "AS-IS" and the information should be used at your own discretion.  The thoughts and opinions expressed are the personal thoughts of Mitchel Sellers and do not reflect the opinions of his employer.

Content Copyright

Content in this blog is copyright protected.  Re-publishing on other websites is allowed as long as proper credit and backlink to the article is provided.  Any other re-publishing or distribution of this content is prohibited without written permission from Mitchel Sellers.