Coffeehouse Thread

7 posts

Forum Read Only

This forum has been made read only by the site admins. No new threads or comments can be added.

.NET 3.0 in VS.NET 2005?

Back to Forum: Coffeehouse
  • User profile image
    phreaks

    if I want to begin building apps against the 3.0 framework, what is the best way to get 3.0 support within VS.NET 2005?

    The VS.NET WPF extensions are from November, surely there are more recent updates (figuring with the release of silverlight?)

    Is this really all I need? http://www.microsoft.com/downloads/details.aspx?familyid=F54F5537-CC86-4BF5-AE44-F5A1E805680D&displaylang=en

    Is there anything 'newer'?

    Also:

    That page list the Microsoft Windows Software Development Kit (SDK) as a prerequisite...

    I can't seem to locate it, I can only find the vista sdk...

  • User profile image
    wkempf

    I doubt there will ever be another update to that.  You'll want to, instead, run Orcas for this.  http://msdn2.microsoft.com/en-us/vstudio/aa700831.aspx

  • User profile image
    jb43081

    wkempf wrote:
    I doubt there will ever be another update to that.  You'll want to, instead, run Orcas for this.  http://msdn2.microsoft.com/en-us/vstudio/aa700831.aspx


    I don't think Orcas has a go live license yet, so I probably wouldn't write "production" code in it.

    The November drop was basically the RTM, so you should be fine using it, I've been. Smiley

  • User profile image
    phreaks

    wkempf wrote:
    I doubt there will ever be another update to that.  You'll want to, instead, run Orcas for this.  http://msdn2.microsoft.com/en-us/vstudio/aa700831.aspx


    last time I installed Orcas, it completely broke my VS.NET 2005 apps.

    I don't think I'm ready to tackle the integration with that approach yet.


    So just use the November CTP?

  • User profile image
    wkempf

    phreaks wrote:
    
    wkempf wrote: I doubt there will ever be another update to that.  You'll want to, instead, run Orcas for this.  http://msdn2.microsoft.com/en-us/vstudio/aa700831.aspx


    last time I installed Orcas, it completely broke my VS.NET 2005 apps.

    I don't think I'm ready to tackle the integration with that approach yet.


    So just use the November CTP?


    1.  Run Orcas in VPC.  You should never run beta software on a production machine, and this includes the November CTP.

    2.  Orcas can target 3.0, so concerns with "go live" licenses shouldn't matter.  After all, 3.0 is released.

    3.  I'm surprised (and skeptical) to hear that November CTP has a "go live" license.  After all, it's unlikely the extensions will ever actually be released.  With Orcas on the horizon, it doesn't make sense to release extensions for 2005.  But, I could certainly be wrong.  Even if I am, however, the November CTP can't be compared to Orcas.  I'd still recommend you develop with Orcas instead.

  • User profile image
    TommyCarlier

    The only difference between .NET 2.0 and 3.0 is the extra libraries, so in theory you could write .NET 3.0 in Visual Studio 2005 without extensions. You just have to add references to the .NET 3.0 assemblies and code everything by hand.

  • User profile image
    keeron

    TommyCarlier wrote:
    The only difference between .NET 2.0 and 3.0 is the extra libraries, so in theory you could write .NET 3.0 in Visual Studio 2005 without extensions. You just have to add references to the .NET 3.0 assemblies and code everything by hand.


    We currently do something similar (no WPF, but needed 3.0 for packaging APIs). Just make sure you reference the libraries you need from 3.0. 95% of our solution is built using .NET 2.0, one project is using some .NET 3.0 libraries.

    You probably need Orcas if you want to use WPF (the designer stuff they are adding in Orcas) or .NET 3.5 (which you can same way as above, just get the framework)

Conversation locked

This conversation has been locked by the site admins. No new comments can be made.