Just a little concept for the next BE release. Really want to get rid of editing on live site and move all under admin. Why put it here and not just stick in the Github repository or Plunker? Because blog supposed to be center of your digital Universe and if not then something is wrong with it and it needs to be fixed. Blog, not the Universe - that is out of scope. Maybe next year.
There has been a lot of activity lately on BlogEngine.NET development that went under the radar, so I want to clear things up a little. Because code moved from Codeplex to Github without much publicity, people don't see any changes in a while and assume project is
dead done. This is exaggeration :)
If you are new to Entity Framework, especially to all new EF7, best way to start is to look at this code from sample application. It shows all you need to know to get rolling: connecting to database, creating a table, inserting and selecting data all in one simple console app.
Bootstrap provides nice lists to display all kind of items your website might need. It is very useful, and because it meant to show just few items it is not paged. Problem is, sometimes I do need it paged. For most cases, it can be just a few rows, but for some it can grow in few dozens.
The basic globalization in ASP.NET pretty simple: you create resource (.resx) file for every supported language and include it in App_GlobalResources. ASP.NET will compile it and load on demand. If you put your resources in labels.resx, in your code you can access individual resource like this
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.
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.
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
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.
This real-time customer analytics service just released public beta 8.0 and I tested it with BlogEngine.NET to make sure they still work great together. If you a fan of statistics then you might like it a lot, this service provides functionality similar to Google Analytics with a stress on real-time activity.
This new extension for BlogEngine will let you save images for multiple albums and display any album in carousel-like fashion in your posts and pages using jCarousel plugin for jQuery. It is light-weight and pretty easy to use. I reused code from NivoSlider as foundation, making few improvements and adding ability to create thumbnail images on the fly
Beta (or RC) version of BlogEngine.NET 2.7 has been released this weekend with some cool new features like extension-less URLs and lots of small improvements and bug fixes. If you want to test drive it, head over to Codeplex site and download