Today is the first day of .NET Conf 2019, a slew of videos are coming out to introduce new and exciting technologies in the world of .NET. I watched some of them and I'm really excited about the improvements in Asp.net Core and C#. Here are a couple of interesting things I learned today.
HTTPS has become a basic requirement for a website, I want to show I added a free SSL certificate from Let's Encrypt to my website running on Azure App Service.
Preview3 brings an architecture that allows you to extend Fanray by creating Plugins, Widgets and Themes in a clean and maintainable way. This new extensibility will keep the system core from being bloated and let others build their own features and applications easily.
This release has minor tweaks and fixes on Widgets, Image Processing and Editor upgrade.
This preview incorporates what I worked on for the past few months, fixes, improvements but mostly a brand new widget system. Widgets provide a way for theme designers to optionally define regions (widget areas) on their theme for end users to drag and drop pieces of UI (widgets) onto these areas to customize their site.
If you develop with ASP.NET Core 2.0 or later and you are using TempData, you may run into a 400 error saying your request headers is too long. I've recently encountered this while writing a blog post, it happens when I try to preview the post.
ASP.NET Core 2.2 recently came out and the one thing that caught my attention was the new IIS InProcess Hosting Model. I saw the demo during this week's Community Standup and couldn't help but agree that this could be a big help to development efficiency. As web developers we all do build solution and refresh browsers a lot and any improvement to shorten the time between making a change and seeing that change is welcoming.
I've done some enhancements and fixes to the Media Gallery. Now you can drag and drop images directly in Composer and they will be uploaded and inserted in the editor.
Thanks to CKEditor5's new media embed feature, now we can embed in our posts YouTube and Vimeo videos.
Thus far I have a single service in Fan.Blog that handles everything, it's called BlogService. As my code grows this becomes less maintainable, with each new feature I want to add to the blog I have to pile on top of this class, not to mention it's less than ideal if there are others working on the same project and everyone modifies one file. So I wanted to break this giant service class into smaller more focused services.