I came across a great article today that explains a little about Entity Framework's (EF) default lazy load settings. At first you may be confused as to why they decided to default to lazy loading relationship objects but if you take a good look it makes sense.

The team behind EF didn't want this *automatic* behavior happening. The reason behind this decision is simple: When architecting a larger project, it is highly important for developers to clearly understand when they are accessing certain resources, such as the database.

You can run into a boat-load of performance/scalability issues if you are not aware of what relationships are being loaded using LINQ to SQL. EF tries to eliminate this issue by defaulting to lazy loading. Read the article for a great example and explanation.

So I had a mishap happen with my project the other day and I decided, finally, to get a version tracking system. I had heard a lot about SVN and used TortoiseSVN occassionaly to get the latest versions of subsonic, jQueryMVC, ffmpeg and a few other projects. So I looked around for something that could integrate well with Visual Studio 2008. I ran across VisualSVN, downloaded the trial, and I'm now hooked! It's a really good price too (I have yet to purchase it though). Anyways, TortoiseSVN allows you to easily create your repository and you get a cool SVNAdmin tool which you can use to backup your repository (in combination with task cheduler).

So if you were like me and you keep hearing about SVN this and SVN that... jump in, the water is warm :) You're wasting productivity by not checking it out!

[04/30/08] There's another great article I bumped into today regarding a move to TortoiseSVN and VisualSVN, check it out here.