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.
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.
Ever since computers have been widely available, we seem to be in a never-ending battle against the
“bad guys” online. They’re constantly trying to hack us, steal our private information, create
fake identities, and so many other nefarious acts. It’s difficult to keep up with all of the
latest details and exploits that you could potentially be exploited by. Here are a few tips to
make your life a bit more worry-free, as well as protect you and your business at the same time.
If you’re in the developer community, and especially if you’re using or near any Azure conversations,
you’ll continuously hear someone suggest Let’s Encrypt when it comes to securing your domain
name. You know, that thing you do to allow your website to use the HTTPS protocol to get that
lock in front of it in the web browser. I’ve tended to use NameCheap.com these days. They’re
cheap like their name suggests, and they’re super easier to use. However, things just got even