1. December 2013 13:12
If you want to try new BlogEngine.NET 2.9 beta
just released to the public, and planning to upgrade your blog, here is little handy utility you can use. Using it pretty simple, just follow these steps and you'll get your blog upgraded in no time. Well, at least I did - no guarantee it will work for everyone, of course. So please don't skip backup and testing and blame it on me :) More...
4. November 2013 11:44
Usually blogs have well known structure, which is understandable; one of the core ideas behind blogs is ability to "talk" to each other using RSS, format that defines very strict set of entries like "post", "category" or "tag". Also common format helps to move data from one blog engine to the other making your data portable - big plus. But there are times when you want to go beyond this limitation, and add something valuable to you and your readers. So there is need to extend blog's data structure somehow to hold this extra data. For example WordPress adds meta tables for most main entities, and you have post meta, comment meta, user meta etc. I don't necessarily like this approach as it tightly binds extensibility points to existing structure. To borrow from famous Rumsfeld's rant, those are "known unknowns", and sometimes we have to deal with "unknown unknowns". Maybe single generic entry where post or user defines a type would be a better choice, because then we could add new type instead of creating new entry (table). This also allows (oh my!) to have meta for meta entries and not just stick another key/value pair into the post or comment. More...
Looking for improvements to layout and theme structure in the next BlogEngine, I went through existing code analyzing how these things work now. Its not very straightforward, so I decided to put together a quick overview that might help someone maintaining and modifying blog built with BlogEngine.NET. More...
BlogEngine.NET 2.8 was just released to the public, and if you feel lazy going through the steps to upgrade, here is how to do it easier. Download little utility from the link in the end of this post, watch short video with example how it works and you should be able to upgrade without breaking a sweat. One thing that is not mentioned in the video is that this utility if it finds issue it will try to fix it and log this into log.txt in the same directory where you run it. You might want to check this log file to make sure it did a correction properly. More...
BlogEngine 2.6 release is out and you might want to upgrade your existing blog to take advantage of all the new features. You can read instructions how to manually upgrade your site or you can try updater utility I've been using lately to automate upgrades for my blog, it worked well for me and chances are it'll work for you too. It doesn't do database part, so you'll need to do some extra work to run database script and update web.config with connection string. For XML provider all you need is follow instructions below.
Lets assume you use c:\upgrade directory for this exercise.
- Download 2.6 release (web), unzip and copy files to c:\upgrade\be26
- Pull your existing blog to c:\upgrade\old using FTP client like FileZilla
- Download and extract BeConsole.exe to the same c:\upgrade directory
- Create new folder: c:\upgrade\blog
- Open command line, change directory to c:\upgrade and run this command:
beconsole -u c:\upgrade\old c:\upgrade\be26 c:\upgrade\blog
The c:\upgrade\blog now should have your blog upgraded to version 2.6 and ready to be uploaded to your host. I tested it upgrading from 2.0 and 2.5 versions and it worked quite well. Let me know if you run into issues and I'll try to improve it more. May be we can plug it into next BlogEngine for one click auto-update, who knows.
Post navigation in BlogEngine is a little hard to customize. By default it looks like picture below and that works fine with standard theme. Small problem is that those angle brackets and "|" in the middle not that easy to get rid of without some nasty CSS tricks because they baked into the core code that nobody likes to touch (or you'll have to remember to carry it over during upgrade). Good news is that you don't have to touch it and still modify navigation any way you like pretty easily if you follow this little guide. More...
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. It just makes sense to have WAP version in some way linked to “proper” BlogEngine.NET so we won’t be reinventing the weal but improve on the single code base instead. More...
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. You can read in-depth about it on Ben's blog, I'm not going to repeat it here. Just want to say - don't dismiss it if you only going to run one blog, it can be helpful in many ways. I for one planning on little family "members only" site working as sub-blog and another used as private Wiki. All on the same code base, with single update cycle - can be a time saver. More...
Just got an email asking about how to install ELMAH on BlogEngine.NET 2.0:
I am trying to use Elmah with BE 18.104.22.168
Keep getting web.config errors one after the other.
Are you currently using it? Could you provide me a web.config for BlogEngine
Come on guys! Installing ELMAH by hand? It’s so 2010! More...
22. December 2010 23:47
Go to hosting dashboard/content/IIS management and click “create” link. This is an interface GoDaddy provides you to create virtual directory for your ASP.NET application. Give a name for directory and don’t forget to check “set application root” – this is akin to “configure virtual directory as application” in IIS world, and this is exactly what we doing - installing ASP.NET application. More...