Converting BlogEngine.NET to Web Application Project has been a popular exercise ever since Microsoft introduced WAP project template for Visual Studio. Without getting into nitty-gritty of arguing about advantages one has over the other, converting from web site to web application is easy enough for BlogEngine.NET community to have both models.
Sometimes you might want to protect individual posts or pages with a password so that only users you sent password to can access this resource. Not exactly wide-spread scenario, which explains why it is not currently supported by BlogEngine. But when you need it you need it, and this extension should cover the basics
I took a plunge and decided to run Windows 8 consumer preview as my main OS. I realize it is beta and expect lots of issues, it is given. If there are real showstoppers I might even go back to Win 7, will see. But for now it looks ok and I want to share experience in case someone else thinking about making a switch.
Let's start by creating new empty ASP.NET website and adding Default.aspx with minimal “hello world” markup. When you access your site and check it with profiler, you’ll see single get request for default page.
Tell me what you want, but CSS is twisted. Some simple basic tasks that should be no-brainer sometimes make you throw things and say words you later deeply regret. Usually people use IE6 as lightning rod, sadly even if you don't care about IE6 anymore CSS still will find ways to hurt you.
Lots of people use Google Analytics to track user statistics on the blog. If you one of them, there is another tool you might be interesting in – something called “Woopra”. Although Analytics are cool, Woopra excels in real-time tracking – it literally shows what is going on your blog right now.
BlogEngine uses NuGet format for sharing extensions. NuGet package in a nutshell is a ZIP containing files you want to share with some metadata NuGet uses internally. The easiest way to create a package is to use Package Explorer. Download and install this small application on your local machine, then click to run as any regular Windows application.
What we need next is to save metadata for each picture used by every slider, and also we need to be able to add and delete all these records. Extension settings are standard way of doing it in BlogEngine - you declare what kind of data you want to maintain, set initial values and first time extension runs it will instantiate settings object and save it on the back-end.
HTML code we added to site.master can be moved to user control (1), so we’ll need just drop control on the page and be done. But some new themes use Razor instead of WebForms – for those to work we can provide HTML helper (2) do the same thing control does for WebForms. And also we want slider be available in the posts and pages, for that functionality we’ll have to use extension (3)
BlogEngine 2.5 final release is ready for download, and most anticipated new feature is obviously ability to run multiple blogs on single code base. It's been a top request for a while, so hopefully it'll make lots of people happy