Nick Harrison poses some good questions about how we learn new technologies and libraries, and suggests a few ways to speed up the process.

I’m starting a new codeplex project to build a fluent library for design patterns. For example let’s take those examples.

An extensive article to understand how dynamic keyword works, limitations and best places to use it

Implement Repository, UnitOfWork with Audit support in Composable Service End

This amazing small tool allows to query SQLSERVER or MYSQL databases using LINQ or simple SQL, doesn't require installation, and works like a charm, really useful if you're trying to learn LINQ. It's just 4MB

I've been playing around with Code First EF implementations for awhile now and by far the best implementation I've seen is a framework by Huy Rua. It has the following functionality baked in: True Separation of Concerns for entities (no need for a data annotations dependency). A Generic Repository....

Simple project featuring usage of EntityFramework CodeFirst and overriding SaveChanges method of DBContext in order to keep record of changes on entities in database. There is a simple usage sample project and a test project with couple of test cases to confirm that everything is working.

Here I have described of implementation repository pattern with EF4 POCO support according to my earlier articles.

Now a days computers are coming with multiple processors that enable multiple threads to be executed simultaneously to give performance of applications and we can expect significantly more CPUs in near future. If application is doing CPU intensive tasks and we find that one CPU is taking 100 %usage ...

Taking a look at how to use the Entity Framework via its model first design concepts. When building out an application which is based off of the Entity framework you have multiple options, you can either build your model off of your existing database or build your database of your existing model....

Code Re-factoring for the sample project attached with the post Repository, Specification, Unit of Work, Persistence Ignorance POCO with Microsoft ADO.NET Entity Framework 4.0 Beta 2. Brief explanation of the changes are included.

This is my second post on one of the ways of applying the Repository, Specification and Unit of Work pattern using the persistence ignorance POCO with the upcoming ADO.NET Entity Framework 4.0. This post will explain how to implement the Repository, Specification & Unit of Work with Entity Frame...

This is my first post on one of the ways of applying the Repository, Specification and Unit of Work pattern using the persistence ignorance POCO with the upcoming ADO.NET Entity Framework 4.0. First part of this post will introduce the Entity Framework 4.0, its features and its comparison to Entity ...

The impact of performance is much more readily apparent in .NET Compact Framework applications. The mobile devices commonly have a CPU that is 10 times slower than your desktop CPU, and possibly up to 100 times less RAM than a desktop or server. In Agile or XP development, the mantra is often to i...