Pssst...Ferdy is the creator of JungleDragon, an awesome wildlife community. Visit JungleDragon

Blogo.NET 1.00 released! »

FERDY CHRISTANT - APR 1, 2008 (08:30:37 PM)

Dear readers,

As of now, Blogo.NET is available for download from my s3maphor3.org open source site. The download includes a detailed manual that explains how to install and use Blogo.NET.

You can find more information about Blogo.NET on the project page. You will find news, the change history, downloads, and screenshots there.

Blogo.NET can be used as a "production" blog engine, yet I do not plan to add new features to it, I'll leave that to you. I do however intend to fix bugs and answer questions. You can request this kind of support from here.

I hope you enjoy Blogo.NET and find it useful in some way. Soon I will come up with the extensive "making of" article, and then move on to a next project.

Share |

Comments: 3

COMMENT: VLADIMIR KELMAN

APR 9, 2008 - 09:06:00 PM

comment » Hi Ferdy! I came here from your comment under Imar Spaanjaars' article http://imar.spaanjaars.com/QuickDocId.aspx?quickdoc=416. We're currently starting to develop ASP.NET version of our company's Intranet using N-layer approach described in Imar's article. We decided to start with using DataReader in DAL with a possibility ti switch to LINQ (or maybe some O/RM like NHibernate) later. I hope to learn from your experience too. «

COMMENT: VLADIMIR KELMAN

APR 10, 2008 - 01:59:44 PM

comment » Ferdy,

What advantage you see in using LINQ to SQL to fetch data from DB and to save data back instead of using SqlCommand/SqlDataReader technique for the same purpose, as it was described in Imar's article? I could only think about increased data type safety.... but I have heard than LINQ is much slower. «

COMMENT: FERDY

APR 10, 2008 - 03:39:40 PM

comment » hi Validimir, interesting...I think indeed one advantage is type safety. This also means you can use type-ahead. Many developers are not really great at writing good SQL, so LINQ helps in this area by treating data as objects.

Furthermore, the chance that you will leave a SQL injection vulnerability open is much smaller. Thos are the things I can think of, in summary: type safety, ease of use, security. «