Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Does anyone know why the .NET Framework version 4 is split into Client Profile and Extended?
Microsoft cites two reasons for having the Client Profile
>
Can be serviced separately.
Does not need the .NET Framework 4 Extended component of the .NET Framework.
These seem flimsy at best to me, and I need to explain why I want both Client Profile and Extended installed on all our client desktops. My best answer now is “I don’t know even know why Microsoft split them in the first place”
Does your client application actually need the “full” framework? If not, only install the client part – which will be considerably smaller. That’s the point of having the separate profile; it’s a smaller install footprint and download time for applications which only use the parts of the framework typically required by client apps.