.NET 4 Client Profile

Sign in to queue

Description

Jossef Goldberg and Jaime Rodriguez discuss the status of Client Profile in .NET 4 and VS2010 beta 2. 

Client profile is a subset of the full .NET framework that includes only the assemblies needed for desktop client applications; the subset decreases download size and improves install time of the framework, improving the overall deployment experience.  

Related reads: 
Jossef's deep dive into client profile
Comprehensive post with all the new features in WPF 4 beta 2.

Embed

Download

Download this episode

The Discussion

  • User profile image
    vesuvius

    It is good to find out that we do finally have a two tier .NET framework.. I know a lot of people that said that it would never happen, but why should every windows machine have workflow foundation/wcf/asp.net etc?

     

    On a brand new Windows 7 machine, that most likey will come with .NET 3.5, will the client profile remove this or will they run side by side?

  • User profile image
    Jaime Rodriguez

    Hi vesuvius,

    Yes, Windows 7 comes with .NET 3.5 SP1. .NET 4 will work side-by-side, so it will leave your .NET 3.5 Sp1 alone.  From there on, you get .NET client profile + full as two skus.

     

    Cheers,

     

  • User profile image
    reinux

    Okay, correct me if I'm wrong here:

     

    So if I want to write an app that uses HttpUtility.HtmlEncode or UrlEncode, the user needs to install the full framework, or I need to roll my own.

     

    A lot of users will be installing .NET twice per version. I can already hear tens of thousands of people screaming "but I thought I already installed .NET 4".

     

    I honestly fail to see how this is a good thing. More versions of .NET for embedded/mobile OSes would be nice, but more versions for Windows just seems silly.

Add Your 2 Cents