.NET and Open Source: better together

RTur.net

  • Join Us on Facebook!
  • Follow Us on Twitter!
  • LinkedIn
  • Subcribe to Our RSS Feed

The Failure of Communication

Explaining is hard. Things that seem crystal clear to you can be completely foreign to others, and when I started planning on Blogifier, concept looked very natural and not even worth explanation. Seriously, the whole “architectural” diagram would look something like this – web application (Blogifier) using component (Blogifier.Core) to encapsulate common blogging functionality.

Nothing hard about it, right? Wrong, I bump into people over and over telling me they have no idea what I’m trying to accomplish. Different people. Smart people. To make things worse, the Core component did a good job pretending to be an application on its own – it has sample app that only needed for testing, but people took it and ran away.

I’m hoping to fix this miscommunication soon. We just released Blogifier.Core 1.2, and this will hopefully be the last “Core” to worry about. Moving forward, this will be what it was supposed to be all along – just a component like jQuery or Bootstrap so you can build your application on top of it.

The application we are building is Blogifier. That is, just “Blogifier”, without “Core”. It is, accidently, a blog. It references Core so it does not have to deal with all the common plumbing, like database, services, APIs and so on. We going to add all the bells and whistles to make it fun modern application everyone would love and wanted to use. It will run on Windows or Linux, have install and, later, in-place upgrade to the latest version. The work just started, but we already have code repository integrated with demo site, so if you are interested in progress and want to make your opinion heard please follow the trail.

Hope this clears things a little bit, if not – don’t hesitate to ask any questions.

Blogifier Release 1.1

It took just a few weeks to move Blogifier to release 1.1. Although changes are mostly cosmetic, it adds some really nice polishing touches to core functionality and significantly improves UX. Check out below what exactly was added in this new version. More...

Blogifier 1.0 has been released

It took way too long but finally Blogifier.Core 1.0 has been released to the world! It means, two brand new packages popped up in the Nuget.org and, if you search on "blogifier" it should return page looking similar to this: More...

Update on BlogEngine.NET

People keep sending me emails asking if BlogEngine.NET is dead. Not surprisingly, given lack of updates since beginning of 2017. So what's going on? As they say, picture worth a thousand words, this one explains where things stand now pretty accurately. More...

Introducing the Blogifier

I've been playing with this idea for a while now, trying different approaches, building proof of concept samples, throwing them away and starting over. Here is scenario I going after: your client asks you to build web application and, when you done, there is a little extra - "can you also add a blog to our website please? The PR people say it might come in handy and we want our product managers to engage by posting news etc. Shouldn't be too hard, right?" Well, you can add Wordpress or alike and call it a day, but what if they want it truly integrated, not another external application but part of website you just built? That would be a challenge. For example, here is 21 step (!) guide on integrating BlogEngine.Net into your application. And this is a challenge I was trying to tackle by creating Blogifier. More...

Export Existing BlogEngine Comments Into Disqus

For some time now BlogEngine supports multiple commenting systems, from built-in to 3rd party, like Facebook or Disqus. Switching from one to another is as simple as selecting an option in the admin. The catch is, if you have existing comments and want to bring them over - you on your own. Here I'll cover relatively painless process exporting your comments into popular Disqus commenting system. More...

Building Widgets for BlogEngine.NET 3.3

Version 3.3 dropped user controls from BlogEngine and new widgets use Razor views instead. To start developing new widget, open source code in Visual Studio, navigate to BlogEngine.NET/Custom/Widgets in the solution explorer and add "Example" folder. If you run application and go to admin/custom/widgets, you'll see "Example" widget added to available widgets. You can even drag it to widget zone and save changes. More...

BlogEngine.NET 3.2 Released

The year wouldn't be complete without it :) It took a lot longer then I hoped, for variety of reasons, but finally went live. New version is much more pleasant to use, it is improved and simplified in many ways. Besides new design, it went through lots of code changes which may not be obvious and this is what I want briefly explain here. More...

Post Paging Extension

Reading this thread on Codeplex I was going to write that no such functionality exists but probably easy to add. But then I though just how easy it really would be? So I fired up Visual Studio and about half an hour later I got functioning plugin that does exactly what requested. And this is why I like BlogEngine - it is insanely easy to customize. At least, when you get used to it because documentation admittedly sucks. More...

Boldy Updated to Version 3.1.1

We getting really close to BlogEngine 3.2 release and I'm mostly switching to integration tasks, checking how it works with external code, like themes, plugins etc. As an exercise I decided to refresh my old Boldy theme and make it work with very latest code. To make things simpler, I took layouts from new standard theme and applied Boldy styles on top of it. The result you can see here on this blog, install from gallery if you running BlogEngine.NET blog or check out code at GitHub.

Also, if you running BlogEngine.NET, I would really encourage download latest version and try it out with your blog to make sure it works smoothly and we didn't miss anything specific to your environment. There were lots of changes to the core base, not just UI, and we would love to catch errors before we go live.