Here’s an end of the year gift for all .NET developers.
.NET 9 officially launched in November. While it’s always possible to deploy .NET 9 (ASP.NET Core 9) apps to the shared cloud hosting platform using Self-Contained Deployment (SCD), you’ll now find .NET 9 installed on the shared cloud hosting servers. So now you can go to town using Framework-Dependent Deployment (FDD).
Happy Coding!
Visit Everleap to learn more about our .NET Core cloud hosting solutions.
Here’s an end of the year present for you .NET developers!
Microsoft released .NET 8 last month. While it was always possible to deploy .NET 8 applications to our cloud hosting environment using Self-Contained Deployment (SCD), we now have .NET 8 (ASP.NET Core 8) installed on our cloud hosting servers. This means that customers can use Framework-Dependent Deployment (FDD) and Visual Studio 2022 to deploy their .NET 8 (ASP.NET Core 8) applications.
Happy Coding!
Visit Everleap to learn more about our .NET Core cloud hosting solutions.
Before I get to the main point of this article, I acknowledge that even though Everleap is the perfect hosting environment for your nopCommerce site, it can be a little confusing for many people.
In this article, I’ll try to cut to the chase and explain why Everleap is the best environment for nopCommerce. And hint: It’s primarily because it is easy to instantly upgrade your site within our environment with pretty much no downtime. Here, let me explain…
In my last blog post, I discussed how you can use CloudFlare to prevent bad bots from getting to your site. But, what happens if the bad traffic still remembers your old IP number for the original web server and the bots still get through.
Recently we had one of our Managed Hosting customers experience this very problem. We helped find a solution to this issue.
I posted previously about recently discovering that some of our Managed Hosting customers running nopCommerce sites were experiencing high traffic with no increase in sales activity. It seemed suspicious, and for those customers using our Advanced Monitoring service, we detected an increase in CPU resource usage and a noticeable slowing down of their sites. As it turns out, the traffic was from bad bots. We contacted our customers, let them know what we saw, and helped them fix the issue.
There are many options to prevent bad bots from affecting your site, but the best and ultimate option to strive for is to prevent the bot from hitting your site in the first place. Here I discuss my preferred method.
Microsoft just released ASP.NET Core 6.0 on November 9, 2021. This is a major release, and the key takeaway is that there is a lot of performance improvements to help make your apps faster and new coding syntax to hopefully make your coding life easier. A complete list of changes can be found here.
Did you know that you can deploy .NET 6 applications to Everleap right now using Self-contained deployment? I’ll show you how to set the publish mode in Visual Studio.
Today we announce that .NET 5 or ASP.NET Core 5 is installed on the Everleap system for Framework-dependent Deployment (FDD). (Note that .NET 5 or any other .NET Core version can always be used on the Everleap platform at any time with Self-Contained Deployment (SCD) – even if the version is not installed on the server.) It did take a little while to get .NET 5 available for FDD on our entire system since we’ve been going through a round of hardware upgrades. I’m happy to say that we’ve finished this round of upgrades and so now .NET 5 is available on all servers.
Unfortunately, this blog won’t be about how to get your hair cut during this COVID-19 pandemic, but it will be about one of my pet peeves, THINGS NOT LINING UP! Or you can say I have OCD. Whateva!
As I have been working a lot with Blazor recently, one of things I found annoying was how validation was styled in the default Blazor Server template. Here I show you how I fixed it.
Over the past few weeks, I’ve been working on updating an old app (or personal website rather) that I developed by rewriting it in ASP.NET Core Blazor. I must say, Blazor, has made my life much easier since everything can be written in C#, and I’ve had to use very little Javascript to implement the same features my old site had. (My old site was very reliant on Javascript and AJAX calls.) I did run into some issues though and wanted to share this quick tip for those trying to implement an upload feature.
Even with the Stay at Home order due to the COVID-19 virus pandemic, we’re still hard at work here at Everleap.
I haven’t had much time to personally explore development in .NET Core until recently now that I’m staying put. I started about a week ago, ran through a couple of Microsoft tutorials, and delved right into it. Immediately, I ran into a roadblock with the connection string because .NET Core doesn’t really make use of the web.config file which I’m used to in .NET Framework. So, something as simple as assigning a connection string to a string using System.Configuration proved difficult.
private static
string connectionString = ConfigurationManager.AppSettings["ConnectionString"];
That’s because .NET Core allows you to pull configuration information from a variety of sources. After researching the matter further on the web and looking at various solutions involving dependency injection and Microsoft.Extensions.Configuration, I couldn’t really find a working solution for what I wanted to do – which was to simply reference it in a class library project apart from the main project (in other words, I couldn’t get the code to work properly in a manner that I am used to), so I developed one of my own solution and am sharing it with you in this post.