The Pain of Living on the Edge

If you’re like me, you tend to listen to Manowar really loudly while you write code and built ETL solutions.

No, wait, that’s another post. Please let me begin again.

If you’re like me, you tend to stay on the cutting edge, upgrading to the latest and greatest development tools as soon as they’re available.

Yes, that’s the right post.

The great things about this tendency are that you get new features and functionality early, you are constantly learning new things, and when the products are actually released you already have months experience using them, so not only do you have a competitive edge, you can also help others who are less adventurous learn things too. All around it’s a real win-win scenario.

But it is not without its pain.

Visual Studio 2008 has recently been released, with important (and cool) new capabilities for people developing Windows and web applications using VB.NET, C# and other “traditional” development tasks. But what about us Business Intelligence developers? Well, do you remember that song from the opening of “Four Weddings and a Funeral?”[1] Well, we’ve been left out in the cold, like Hugh Grant. The current CTP5 release of SQL Server 2008 still relies on Visual Studio 2005, so if you want to get the goodness of Visual Studio 2008 when building SSIS packages, you’re out of luck.

…but like with Hugh Grant, there is a happy ending in sight. Michael Entin, a member of the SSIS product team, posted this information today on the SSIS Forums on MSDN:

1) SSIS 2005 requires VS 2005, and will not work with VS 2008.
2) SSIS 2008 RTM will work with VS 2008 (and only with VS 2008 – there will be no option to use it from VS 2005).
3) It is not final yet when this will be implemented, most likely the next CTP will use VS 2005, and there will be a refresh that provides VS 2008 support.

Michael was careful to point out these these plans are tentative and subject to change, but it’s still exciting to know that there is a plan and a roadmap for getting the tools we want hooked up with the BI projects we need and love. Now let’s just hope that Visual Studio doesn’t marry a rich old Scottish gentleman before then…

[1] In case you missed that one, it was “But Not For Me” by Elton John and went “they’re singing songs of love, but not for me…”

Advertisements

About ssimagine

My name is Matthew Roche, and I am a Senior Program Manager with the SQL Server product group at Microsoft. I work on Master Data Services and Data Quality Services, and have previously worked on SQL Server Integration Services. Although I work for Microsoft and will be posting on technical topics, I want to stress that this is a personal blog, and any opinions posted here are mine and mine alone. I built my career around SQL Server and Microsoft technologies for well over a decade before I joined Microsoft as an employee, and I plan on using this blog to share my personal experience and opinions. They may well be shaped by my experience on the SQL Server team, but they’re still mine, and not that of Microsoft, disclaimer, disclaimer, etc., etc..
This entry was posted in dev, Katmai, SQL Server. Bookmark the permalink.

2 Responses to The Pain of Living on the Edge

  1. 1a — I believe you’ve misspelled “Gershwin”.

  2. Weird – usually my spell checker catches things like that. Weird that the CD description on Amazon had the same misspelling. Perhaps they use the same spell checker…

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s