26 January 2013 CI Team Edit


With .NET 3.5 they’ve published two new deployment-methods for the framework:

  • Full Framework

  • Client Profile

Shortcut: With .NET 4.5 the construct that caused us all a lot of headache is gone.

Why all this?

The initial idea was to create a totally new and slim Framework. Other ideas might be about the security because why should a client pc provide components for server applications?

The problem

As a web- or “server” developer you are usually never get in touch with the .NET client profile. It will be a problem if you try to take some components from a “client profile” application which might have some kind of reference on the whole big framework.

You will find a nice overview about the subject on the Stackoverflow answers.


.NET 4 client profile application:


As far as I remember Visual Studio 2010 doesn’t act as clever (what lead to this errors) as Visual Studio 2012 and didn’t show this hint:


With .NET 4.5 there isn’t a client profile

“Starting with the .NET Framework 4.5, the Client Profile has been discontinued and only the full redistributable package is available. Optimizations provided by the .NET Framework 4.5, such as smaller download size and faster deployment, have eliminated the need for a separate deployment package. The single redistributable streamlines the installation process and simplifies your app’s deployment options.”

Source: MSDN



blog comments powered by Disqus