Browse by Tags
All Tags »
Versioning and Compatibility (
RSS)
It's kind of a pain in the butt to have to compile stuff to two different versions of the Framework. I haven't dived into Whidbey too much, but I sure hope MSBuild lets you define which version of the Framework you want to target (I'm pretty sure it does...
Building a Better Server Control Experience, Part 2 The Devil's In The Details: It's The Little Things That Make Customers Happy Details matter. Especially in building solutions people pay for. You've heard of the term WYSIWYG? Well why isn't the term...
My fifth article for Builder.com is now online . This is the first of a three-part series on .NET Compatibility. These articles stemmed from my “No-Brainer Compatibility” rant, and will hopefully provide a crystal clear explanation as to how to tackle...
For several weeks now, I've been talking about various issues in regards to component versioning and Framework compatibility. A few months ago, I got so frustrated by the issues that were raised, that I said I was going to start a task force to solve...
Paul Alexander was kind enough to put together a series of really slick graphics elements that were designed to denote which version of the .NET Framework a particular component was compiled to. This is ideal in situations where you either a) only have...
Frans says: That's all fine what MS thinks I should do but what I think MS should do is make their IDE able to work with older CLR's so people can choose a new IDE while writing a control for 1.0 or 1.1. MS didn't even bother creating a config file for...
More Posts