Jeff Makes Software

OK, so admittedly I've questioned the usefulness LINQ to SQL, but I'd never stand up and say that it's gotta go. What was really said at PDC? Sure, the entity framework sounds super (I say "sounds" because the write ups for it on MSDN are terrible, and the very few books on it haven't been released yet), but why would you stop supporting something that is so obviously gaining momentum and fandom?

Well that didn't take very long, did it? New gig, no work, back to the streets I go.

It seems like the most talked about thing on the street for code monkeys coming out of PDC is the introduction of dynamic typing. I'm trying very hard to understand why this is a good idea. Nikhil Kothari makes a good case for it interacting with Javascript from Silverlight, but that strikes me as a fringe case. I guess there's a part of me that is curious to know if this came out of a science project or actual customer need.

I know a lot of .NET devs are converts to Mac hardware, but if you haven't made the leap yet, Amazon has a $100 rebate on them now, and there's no sales tax. That's at least $200 saved versus buying in the Apple Store.

When we last left our heroes, we talked a bit about cutting up a single image for the purpose of serving tiles to a MultiScaleImage (Deep Zoom) in Silverlight. The motivation in this case is to offer some other means of serving the images, like from a database, instead of the mess of files that Deep Zoom Composer generates.

Wow, I can't believe three weeks passed since my last post. This is clearly the problem with a day job that doesn't align with your interests!

I've been trying to put together a couple of articles on rolling your own Deep Zoom viewer, fed by a database with images all cut up for you. The image cutting I've got, the data I've got... but the MultiScaleImage control is not working as expected.

I've been playing around with LINQ to SQL lately and I found an issue that I can't quite get my head around. Perhaps you can help.