>>>I guess I interpret the version C#2.0 to mean C#2005. C#2008, in the same vein would be C#3.5 - but I'm nitpicking. Now you've got me wondering whether one can use VS2008 to build C#2005 applications :-}
>>
>>Dunno whether this will answer your question, but ..
>>In the project properties (where one specifies the assembly name and default namespace), there is a Target Framework
>>Choices are
>>- .Net Framework 3.5
>>- .Net Framework 3.0
>>- .Net Framework 2.0
>>
>>So, my guess is Yes, you can
>
>Getting into some thread drift here ... <g> ... I've been looking into this too. Yes, you're right, that's what that whole Target Framework thing is for. However, my complaint about it is that's only something that can be set for the Project, not the Solution ... at least I haven't found a way to do it yet.
>
>So, if I convert a VS2005 solution to VS2008, the default behavior is to target the 2.0 Framework. This means, if I want to target the 3.5 Framework, that I have to hit each and every project and change the Target. This is a bit ridiculous if you have as many projects as we do (in more than a few solutions).
>
>Of course, this may imply that it doesn't matter which Framework version I target ... this is the next thing I'm trying to find out. If I leave my applications targeted to the 2.0 Framework, will that continue to work for many years or will the next thing MS comes out with require me to target 3.5 at a minimum. Haven't found the answer to that one yet.
>
>~~Bonnie

hi Bonnie,

Do not ask me very difficult questions - for I am a novice still

But since (most of) 3.5 builds on 2.0 (and 2.0 on 1), I think you'll be safe for many years to come.


otoh, isn't there a way to automate the rebuild of a project/solution ?