We "Upendo" to Write for You!
Our team loves to share our thoughts, research, experiences here in our blog. Please enjoy our articles and leave a comment to let us know what you think.
If you've been watching the journey of Hotcakes Commerce over the years at all, you know that it has a very interesting past. It began as a different platform altogether. It became a wildly successful commercial e-commerce solution that consistently was in the top 3 products in the DNN Store. It then became an open-source e-commerce platform, making it freely available to the world. This is the solution you're reading about and know about today.
Every ASP.NET application has no less than one website configuration file - also called the web.config, since
that's what the name of the file actually is. We often get asked a lot of questions about how to properly
check-in the web.config and how to safely distribute the file across environments and developers. This
article is going to disclose one of the tricks that we use for our clients.
Depending on who you ask, you’ll be the recipient of a very passionate response when you ask any DNN’er their opinion
about DNN upgrades. In general, upgrading DNN is very similar to any other ASP.NET application. Yet,
when things go wrong, people tend to blame the application itself. Don’t get me wrong, the respective application
can and sometimes does have something to do with an issue that may occur, but in my experience, that’s the exception
and not the rule. Here are some tips to help you have a less "exciting" time the next time you have to upgrade