I've been working on a project with WCF in Visual Studio 2008 and it of course includes all the tools for .NET 3.0 for setting up WCF services and Service References as well as WPF support. It works great. Unfortunately my customers are not running VS 2008 yet and they are - justifiably so - weary to jump onto the latest MS bandwagon. Well, there's that and the fact that VS 2008 is not available outside of MSDN at this point.
I'm happily using VS 2008 and truthfully this release is more stable for me than VS 2005. Maybe more importantly it has all the tools I use in one place one install, vs. the 10 or so installs you have to go through with Visual Studio 2005 from SP1 plus all the extensions for .NET 3.0 etc. Regardless it'll take a while before my customers are on the VS 2008 bandwagon. So I was planning on just taking my 3.x project and putting the project in VS 2005 just to compile etc. And it worked fine back porting to VS 2005 with two little project tweaks: Changing the solution file and for this .NET 3.0 application changing the build target in WCF project.
One problem however: When I installed VS.NET 2005 on this machine I did a purely minimal install. So out of the box there's no .NET 3.0 support. Took a while for me to realize though (how quickly we forget when using a simpler tool). Now mind you the code compiles just fine, but there's no way to update the service reference and there's missing support for the
So off I go looking for the .NET 3.0 extensions for Visual Studio. Searching, and running only into the November CTP. I keep looking for a while, nope nothing newer until a bit later and some MSDN forum messages confirm the November 2006 CTP is the last release of the extensions for Visual Studio 2005. .NET 3.0 has been out what - over a year in RTM and late last year - November to be exact and Microsoft released a CTP of the tools for Visual Studio right at the launch.
But these tools were never updated and more importantly never released officially. They still bear the CTP nomer. This means that if you're using VS 2005 you have what amounts to beta software to do anything related with .NET 3.0. The tools are fine - they work (at least the WCF components - the WCF stuff is another story), but it sure sucks to tell customers to go and download a CTP SDK so they can use the tools in their projects. The least Microsoft could have done is to pretend they are done with the tools for 2005 and republish the tools without the CTP designation. But I guess even that kind of pretense was too much effort...
Ugh... no doubt VS 2008 is the way forward and I understand that things have to move forward at some point, but it'll take a while for developers to catch up. It doesn't help Microsoft's image to appear to ram VS 2008 down customer throats by abandoning the VS 2005 so quickly for existing tools especially given that the last update was over a year before the release of VS 2008 to RTM.