I thought that was what the Client Profile was meant to do - the .NET framework would be the default server version. Even the title suggests it. Loads of people are interested in it, in the blogosphere, because they think it solves this exact problem.Maddus Mattus said:Maybe they can make a .Net server and a .Net client version for 4.0?
That would solve your problem
I also think that they should have included the Silverlight runtime in this - or the ability to update it automatically - as that again is part of the "client profile", albeit for the interweb. It is such an obvious thing for me that a client application should have an additional 4MB Silverlight, rather than 100MB server stuff that will never be used.
If you think of the 100 million+ Vista machines with ASP.NET and WCF that will never use it, yet had they Silverlight or a profile that updated itself to just the features that are needed. I guess that is dreamland.