Visual Studio 2008 released!

Hot off the presses, you can get it now from MSDN subscriber downloads or the trial version.  See Soma's blog for more details on the new features, etc. 

Surprisingly, being a WF and BizTalk guy, I'm least excited about the WF/WCF integration.  I'll talk more about what I dislike later, but this is a happy post!  I'm jazzed about the new web models in WCF if only because it provides a nice affirmation of the extensibility of WCF.  I might not like all of the details of how they have accomplished things, but the CSD team has certainly shown that WCF is a solid platform with all the extensibility hooks you need. 

I'm also excited to spend some time with LINQ now that I'll have the bits on my main PC (I have only put the beta on VMs or my secondary machine in my office).  Like everyone else, I've done the simple examples to get some data out of a database and bind it to a UI, but I really want to dig in and see how it works after I have some code written and want to change something in the database. I want to see what the visual modeler/designer can and cannot do, and how using XML files might benefit me more than using the simple path that is there in V1.  

The main thing that really sells this, and some folks don't know this, is that VS 2008 and .NET 3.5, build on the existing .NET 2.0 framework.  So, it should be close to a no-brainer for organizations to upgrade because they can still build their 2.0 applications without having to worry about using 3.5 assemblies if they use the multi-targeting correctly in VS / MS Build.  That's right, there are only additive changes and bug fixes in 3.5 and it uses the same 2.0 runtime that you are using today.  So there should be no issues with breaking changes to core things like datasets and remoting like there were moving from 1.1 to 2.0.  I'm upgrading all my boxes to take advantage of the new features and perf improvements.  The only reason I could see for not updating is if you have other tools like BizTalk or Commerce Server that depend on the 2005 version.  Then you can run both side-by-side, and maybe strip out some of the tools from 2005 that you no longer used to free up some space on your hard drive.   

So, download, enjoy, and happy coding! 


Posted Nov 19 2007, 05:25 PM by matt-milner

Comments

Jun wrote re: Visual Studio 2008 released!
on 11-20-2007 11:09 AM
Matt,
Can we develop BizTalk 2006 inside Visual Studio 2008?
Matt Milner wrote re: Visual Studio 2008 released!
on 11-26-2007 12:05 PM
As far as I know, you still need to use Vs 2005 for the BizTalk designers. The tools were built for 2005 and not 2008. I haven't tried installing with only 2008, but I don't have any indication it will work (which is unfortunate, as it would be nice to be able to remove 2005 all together to reclaim some disk space).
Ram wrote re: Visual Studio 2008 released!
on 12-18-2007 2:31 AM
what are the new Feature are Available in this Visual Studio 2008
Matt Milner wrote re: Visual Studio 2008 released!
on 12-21-2007 1:45 PM
Ram, you can find a pretty good rundown of the new features on Scott Guthrie's blog [1]. His is a good blog to watch if you want to know what is happening with current and emerging technologies and products.

[1] http://weblogs.asp.net/scottgu/archive/2007/11/19/visual-studio-2008-and-net-3-5-released.aspx
Wouter Crooy wrote re: Visual Studio 2008 released!
on 03-08-2008 4:49 AM
Hi Matt,

Can you tell us, why you're not so excited about the WF/WCF integration. I had to get used to some stuff as well and there's still some thing I can't figure out yet. But on first hands it seems ok.
Matt Milner wrote re: Visual Studio 2008 released!
on 03-11-2008 8:59 PM
Wouter,
Being a BizTalk guy, I miss having true message/content based routing and hate the idea that my clients have to manage a GUID and send that along with their message. I'd like a really nice extensible model for plugging in custom code, where I can manage correlating a message to a workflow instance. However, the way they designed the routing, most of it is closed and I have to write a custom WCF channel to do custom correlation. I also dislike the fact that I can't share a workflowruntime across service hosts if I choose, but that is a little more acceptable. There are some other limitations with the activities that would be OK if we could create derived activities, but of course we can't. So I have a few issues, but generally it is a good start. I'm looking forward to Oslo, when the hosting story gets better for WCF/WF.

Add a Comment

(required)  
(optional)
(required)  
Remember Me?