CS2008: The good news and the not so good news
Hey Everyone,
It's been quite a while since I've had much news about CS as I've been working on other projects, but that should be changing for at least the next few months, which is part of the good news. I'm going to be working on a CS related contract and I will also be working on the CS2008 version of the calendar control in my spare time. The not so good news is that I am seriously considering the option of not upgrading any of my CS sites to CS2008, though I do have one internal CS2008 site for development purposes.
The project that I will be working on is using CS2007 and the customer has made a firm decision to not move to CS2008. The major reason that I and others are considering this is because upgrading to CS2008 is a major undertaking and it is also a major change from the original direction of CS. Performance issues aside (as they can be worked out), CS 2008 doesn't feel like a full product release. It feels more like a stepping stone to an unknown future. The current licensing model has made it impossible for small businesses and some mid-sized businesses to afford CS, and if I upgrade this site to CS2008, I will no longer have the .NET Community license that I have with CS2007. I would be in direct violation of the current CS2008 license.
What does this mean to you? Well, it means that this next release of the calendar control may be the last. The initial release may have more bugs than usual as I'll be the only tester prior to it being released, and bug fixes may take longer to find and fix. I have a feeling that Telligent is going to add some sort of calendar functionality to CS in the not to distant future, so this may only be a short lived issue, though there will definitely need to be some sort of conversion from this control to whatever Telligent may provide. As things progress, I'll try to keep everyone up-to-date.
My next blog post will cover how I am using TFS to manage multiple branches of CS and how it makes it easier to selectively merge SDK updates into these branches. TFS has 2 way merging, which means that you can merge up to the root (inverted tree) or down to any branch while only affecting the 2 branches that are being merged. Source control covers only about 25-30% of what TFS is as it is an Application Lifecycle Management (ALM) application that covers builds, documentation, testing, tracking, and a lot more.
Take it easy,
Bill