Darius Kucinskas
By:Darius Kucinskas Posted On: Topic:Engineering
Darius Kucinskas
By:Darius Kucinskas Posted On: Topic:Engineering
Darius Kucinskas
By:Darius Kucinskas Posted On: Topic:Engineering
Darius Kucinskas
By:Darius Kucinskas Posted On: Topic:Engineering
Darius Kucinskas
By:Darius Kucinskas Posted On: Topic:Engineering

Entity Framework 6 vs NHibernate 4

This article is dedicated to discussing the latest releases of the NHibernate and Entity Framework. NHibernate is (was?) a number one ORM Framework for ages. Its feature list is growing and some things such as code-based mappings and automatic migrations have found a place in Entity Framework.

Darius Kucinskas
By:Darius Kucinskas Posted On: Topic:Engineering

Lesson learned in refactoring ASP.NET MVC3 routes

Typical ASP.NET MVC applications will not face performance issues related to routing. General applications will have one default route ({controller}/{action}/{id}) and several custom ones. Our own custom-built CMS catches all non-custom routes. Therefore, we added a separate and distinct root for every action. You can say that our application is not a typical one – it has a large number of custom routes (approximately 300). Why do a large number of routes lead to performance issues?

Darius Kucinskas
By:Darius Kucinskas Posted On: Topic:Engineering

Devbridge Standard Web Project Template (Part 1)

Our Standard Web Project Template serves two purposes: to share expertise between developers and to make it easier for new team members to setup new web applications correctly. Here at Devbridge, we believe in open communication and like to share our knowledge with others who may find it helpful.  You can always get the latest version of StandardWebProjectTemplate from github.

Darius Kucinskas
By:Darius Kucinskas Posted On: Topic:Engineering

Github Repository You Should Watch: FluentMigrator

MOTIVATION Jeff Atwood in his blog post Get Your Database Under Version Control wrote the following: The database is a critical part of your application. If you deploy version 2.0 of your application against version 1.0 of your database, what do you get? A broken application. And that's why your database should always be under source control right next to your application code. You deploy the app, and you deploy the database. Like peanut butter and chocolate, they are two great tastes that taste great together. This pretty much summarizes my motivation to use FluentMigrator.

Let's Talk