Information
The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

.NET Framework Client Profile Errors

Updated: July 2008

Visual Studio 2008 Service Pack 1 (SP1) lets you distribute a lightweight .NET Framework runtime, known as the .NET Framework Client Profile, which is a runtime that includes just a subset of the binaries that are contained in .NET Framework 3.5. By using .NET Framework Client Profile, you can distribute a smaller .NET Framework library to the users of your application, and the users can run the application even if the full .NET Framework 3.5 is not installed on their systems. For more information about the .NET Framework Client Profile, see .NET Framework Client Profile.

If your application tries to reference functionality that is contained in an assembly or dependent assembly that is not included in the .NET Framework Client Profile, run-time error messages may occur. (The exact message depends on where the referenced functionality is located.) To eliminate such errors, you can either remove the incorrect assembly reference from the project, or set the project to target the full .NET Framework version 3.5 instead of the .NET Framework Client Profile subset library.

If an error occurs because dependent DLLs are missing from the project, you can either add the missing DLLs to the deployment project or remove the references that depend on the DLLs.

NoteNote:

If the referenced functionality is contained in a DLL other than the .NET Framework 3.5 library, you can ignore this message and deploy the application as-is if you are confident that the missing dependent functionality is not called by your code. The message is provided only to remind you about this design consideration.

If an error occurs because the project, or an assembly in the project, references functionality available only in the full .NET Framework version 3.5 library, but the project targets .NET Framework Client Profile, then you must either remove references to the full .NET Framework version 3.5 functionality or target the application to the full .NET Framework version 3.5.

Date

History

Reason

July 2008

New topic to address errors that can occur when targeting the .NET Framework Client Profile.

SP1 feature change.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

Show:
© 2014 Microsoft