I live for these types of conversations: “Hey, is there a way to upgrade my application to the new framework?” The answer is almost ALWAYS no, because the person asking me has already searched the web and is looking for some secret upgrade technique from me. This time, this conversation, well it was a bit more interesting.
“Hey Jeff, Blazor Server-Side and ASP.NET Web Forms are pretty similar in concepts. They both render code on the server and both have a component-based model. Is there a way we could somehow re-use markup between the two frameworks?” That question not only got my interest, but also started some interest with my colleague Dan Roth. We were planning to go on stage at Microsoft Ignite 2019 and talk about Blazor for Web Form developers… when Dan had the idea: “What if we had a shim, a component library that LOOKED and rendered HTML like the original ASP.NET controls? That could help with migration.”
When working with Docker, most folks are very familiar with deploying and building Linux-based containers. ASP.NET Core is a web framework that works great on both Windows and Linux, and can run on both the cross-platform .NET Core framework and the classic .NET Framework. Last week, I was asked about how to package that ASP.NET Core application such that it runs on .NET Framework on a Windows-based container with IIS. I took some time on my live-stream show and walked through the process.
I’ve been thinking and working with application configuration in ASP.NET applications for years, and its become a tool that I’m very comfortable using. I can add AppSettings, create configuration sections, and manage connectionstrings without thinking twice. However, there is a problem with the current ConfigurationManager and the XML-based config file offering in the .NET Framework: how do I get configuration entries from other sources into my application so that I don’t need to build my own configuration client and tools? Continue reading →