>>>>When I create a new WPF project, VS creates it targeting the .NET Framework 4 Client Profile, instead of .NET Framework 4.
>>>>
>>>>Anyone know why?
>>>
>>>(a) Because those DLLs are all that you would normally need at runtime - for WPF or WinForms apps (most of the stuff that is excluded is ASP.NET related)
>>>(b) The Client Profile is part of Windows update so in many cases will already be installed on target machines.
>>>
>>>>Can I change the default that it gets set to for new projects?
>>>
>>>Unless you actually find that some functionality that you need is missing I'd leave well alone. If you really must then, AFAIK, the only way to change the default option is to hack the WPFApplication.csproj template.....
>>
>>The problem is that when I have multiple projects in my solution, the namespaces are not being resolved unless I set all projects to .NET Framework 4.
>
>Do you mean the DLLs listed in a projects references? Which DLLs in particular ?
>IAC if you really need the DLL in question you should only have to switch the project in question to full .NET 4 - other projects which target the ClientProfile should be able to use it without complaint.......

No, I have multiple projects in the solution. I have referenced those projects, not the Dll's, the projects themselves. Then in the code when I specify the namespace, IntelliSense opens and shows the other project's namespace, then dissappears.

If I change the frameowke to .Net 4, it all works fine.