All geek questions in one place

Profile support for .NET Framework 3.5 SP1?

Are there any design considerations you need to take when setting up your .NET Framework 3.5 SP1 client profile? I know this is a subset of the full structure, but what is missing and how do I know if my client profile or full structure will require my application? Has anyone successfully developed an application using a client profile that can share their thoughts on this?

+2
source share
2 answers

The client profile basically lacks server-side things, i.e. ASP.NET and the like. You can simply develop for the client profile and let the compiler process the rest (you will receive warnings if you use something that is not available in the client profile). And if you can’t do anything, switching to the full structure is just a click on the checkbox.

+2
source

You only need .NET Framwork 3.5 if you are considering using LINQ and the ADO.NET Entity Framework or the new System.Addin namespace.

.NET Framework Stack

When creating a new project in Visual Studio 2008, you can select the target structure. This will automatically show or hide namespaces that are not available for the selected version.

-3
source

Source: https://habr.com/ru/post/1716177/

More articles:


All Articles