Decide on which .NET framework version to target

[GoogleCodeExporter]

Currently some of the Sample projects in the solution are using .NET 4.0, while 
others are e.g. using .NET 3.0.

We should target one uniform framework, or at least change all projects to use 
only the framework they actually require (most/all? of the projects don't use 
.NET 4.0 features). 

This should be done because the code otherwise won't compile on the standard 
mono version provided within Ubuntu repositories. I recommend using .NET 2.0 
for all projects unless newer features are required, as this version is the one 
still most likely to be used. 

Compiler features introduced in newer .NET versions can still be used, even 
when an older .NET framework is targeted.

Original issue reported on code.google.com by mlin...@google.com on 13 May 2011 at 3:28

[GoogleCodeExporter]

In the Google.api and the generated file we cannot rely on .Net4
So that anyone still on 3.5 can use our library with out issue.
I am less fussed if some of our sample use .Net4 but like you say only target 
if they need .Net4 features

Original comment by davidwat...@google.com on 13 May 2011 at 3:43

[GoogleCodeExporter]

We should be targeting the .NET 2.0 runtime; .NET 3.5 classes are okay so long 
as Mono will compile them in a *fully supported* (i.e. not in beta) way. That 
way, we can be sure we are targeting the widest audience.

Original comment by jsch...@google.com on 25 May 2011 at 8:52

[GoogleCodeExporter]

We will go with .NET 3.5 for the moment, and try to switch to the .NET 3.5 
Client Profile as soon as possible.

Original comment by mlin...@google.com on 1 Jul 2011 at 6:16

• Changed state: Fixed