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.
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.
Changing the .NET Core version in your web application within the same Target Framework is fairly straightforward, and this article will show you how.
For our customers who are having trouble deploying .NET Core applications to Everleap’s cloud hosting system, I’ve compiled a few tips that will hopefully help you save hours of frustration getting it deployed: