R – Supporting .NET Framework 3.5 SP1 Client Profile

.net-3.5.net-client-profilenet

Are there any design considerations that need to be made when targeting the .NET Framework 3.5 SP1 Client Profile? I know it's a subset of the full framework, but what is missing and how will I know if my application will require the Client Profile or the full framework? Has anyone successfully developed an application using the Client Profile that can share their thoughts about it?

Best Answer

The Client Profile is mainly missing server-side things, i.e. ASP.NET and the like. You can just develop for client profile and let the compiler handle the rest (you'll get warnings if you use something that is not available on client profile). And if you can't do anything about it, switching to the full framework is just a click on a check box.

Related Solutions

.net – Alternative to HttpUtility for .NET 3.5 SP1 client framework

Found today from this here little site that HtmlEncode/Decode can be done using System.Net library in C# 4.0 Client Profile:

Uri.EscapeDataString(...)
WebUtility.HtmlEncode(...)

Edit: I re-read that the question applied for the 3.5 Client Framework but maybe this can be useful those who have updated 4.0..

Wcf – Could not find default endpoint element

"This error can arise if you are calling the service in a class library and calling the class library from another project."

In this case you will need to include the WS configuration settings into the main projects app.config if its a winapp or web.config if its a web app. This is the way to go even with PRISM and WPF/Silverlight.

Best Answer

Related Solutions

.net – Alternative to HttpUtility for .NET 3.5 SP1 client framework

Wcf – Could not find default endpoint element

Related Topic