Amazon.com Widgets

.NET Framework Client Profile

As I mentioned a few days ago, with .NET Framework 3.5 SP1 Beta we are taking some MAJOR steps toward making it easier for customers to acquire the .NET Framework. One of the ways we have done that is creating a client profile of the .NET Framework that includes only those parts of the framework that are relevant to client developers.  image

Several customers have asked me recently exactly what is in this subset.  Well the good news is it is a very large subset of what you need in a client application.  We profiled tons of client apps to be sure we got the right set.   But we'd also love your feedback.  Justin Van Patten has recently blogged out the official list of what is in this profile.   This includes WPF, WCF, WinForms, System.Data, etc...  Please check it out and give us your feedback.

Customers have also asked about the details of the development experience.  How do you target this profile?  How is it deployed? How does it work on different versions of Windows?  etc.   Troy Martez has done a great post that walks through all the details on targeting the .NET Framework Client Profile.  We'd love your feedback on this as well!

Enjoy!!

Published 21 May 08 09:47 by BradA
Filed under: , ,

Comments

# Mojtaba said on May 22, 2008 3:02 AM:

i am waiting eagerly for final release.

# Rory Becker said on May 22, 2008 6:22 AM:

Wouldn't it make more sense to detail what is going to be removed/missing from the client version of the framework which would otherwise be present in the full set.

# Visual Studio Hacks said on May 22, 2008 9:28 AM:

My latest in a series of the weekly, or more often, summary of interesting links I come across related to Visual Studio. Carlos Quintero posted links to help solve a System.UnauthorizedAccessException when registering a Visual Studio add-in for COM Interop

# Rolando said on May 22, 2008 10:13 AM:

I would also like to hear news about the Windows Server Core version of the .net framework

# BradA said on May 22, 2008 10:36 AM:

>> Wouldn't it make more sense to detail what is going to be removed/missing from the client version of the framework which would otherwise be present in the full set.

Rory - You make a good point... I will see if we can get that posted as well.

# BradA said on May 22, 2008 10:37 AM:

>>>I would also like to hear news about the Windows Server Core version of the .net framework

Rolando - Yes!  We are also actively working on this...  Nothing I can announce right now, but it is certainly a priority!

# Charlie Calvert's Community Blog said on May 22, 2008 3:24 PM:

Rather than place the links to the most recent C# team content directly in Community Convergence , I

# POKE 53280,0: Pete Brown's Blog said on May 23, 2008 9:50 AM:

Justin Van Patten from the BCL Team has put out an official list of what assemblies will be included

# Community Blogs said on May 23, 2008 4:40 PM:

Justin Van Patten from the BCL Team has put out an official list of what assemblies will be included

# Sam Gentile said on May 25, 2008 11:51 AM:

Co-Workers Mark Bosley is finding out that Reflector is the Swiss Knife of Workflow programming Meanwhile

# Ekin said on June 10, 2008 11:23 AM:

Hi,Brad,

   I am working in Application Compatibility team, and i want to know what different between .NET FX 3.5 SP1 and .NET FX Client SKU.  because i need to give a presentation to my team.

   Could you share some docs to me. you can reach me by this alias: v-yequnj

   thanks in advance.

# BradA said on June 11, 2008 12:29 AM:

Ekin - check out this link and let me know if that covers it for you or not.. http://blogs.msdn.com/bclteam/archive/2008/05/21/net-framework-client-profile-justin-van-patten.aspx

If you have specific questions you can email me directly

# DEVELOPMENT SITE - NOT MY PUBLIC BLOG said on June 29, 2008 12:02 AM:

Justin Van Patten from the BCL Team has put out an official list of what assemblies will be included in the RTM of the .NET Framework Client Profile. The usual suspects are there, and as expected, server-side technologies like ASP.NET are not. Note that

# Qwe said on June 29, 2008 8:05 AM:

> Windows Server Core version of the .net

> framework

Very, very bad idea to pollute what should be a core OS functionality without all the WMI + 50 services bloat with .NET. If you do introduce it please, please, make it always optional.. core needs to be cut down much, much further to compete with Linux performance on network, filesystem and more..

# BradA said on June 30, 2008 5:45 PM:

Yes Qwe -- the plan is to make it optional.  

New Comments to this post are disabled

Search

Go

This Blog

本博客中文版 (View in Chinese)



These postings are provided "AS IS" with no warranties, and confer no rights.

Syndication

Page view tracker