VS2008 Target Framework
-
If I were you, I'd take a copy of the solution file, then change for one project. Then compare the two solution files (or project files, or wherever the setting is). If the change is simple, then use a text editor with search/replace functionality to "just do it". :) [edit]Haven't you been long enough in this business to know that in the end, Microsoft gui tools just don't work right, and that the text editor is the most precious thing you've got? :-D[/edit]
Joergen Sigvardsson wrote:
If I were you, I'd take a copy of the solution file, then change for one project. Then compare the two solution files (or project files, or wherever the setting is). If the change is simple, then use a text editor with search/replace functionality to "just do it".
:sigh: I figured. So why is it that within 5 minutes of using the product, I find a major deficiency in it with regards to migrating VS2005 solutions to VS2008? Marc
-
What do you intend to achieve? Remember that .NET Framework 3.5 uses .NET Framework 2.0 runtime. As per my understanding unless you are using LINQ features there is no need to change the target? You can still use Anonymous types and Auto implemented properties with target framework of 2.0. Setting the traget framework to 3.5 just adds new references to System.Core which can be done manualy on an as needed basis. Of course you can write a macro quickly to change target framework of all the projects in a solution.
Co-Author ASP.NET AJAX in Action CP Quote of the Day: It is the same Friday that blooms as a new enriching day with novelty and innovation for us every week. - Vasudevan Deepak Kumar
Rama Krishna Vavilala wrote:
What do you intend to achieve?
I want to compile against the latest framework so I can test it.
Rama Krishna Vavilala wrote:
As per my understanding unless you are using LINQ features there is no need to change the target?
I may use them in limited situations.
Rama Krishna Vavilala wrote:
Of course you can write a macro quickly to change target framework of all the projects in a solution.
Why TF should I write a macro?!?! Isn't this something that some intelligent person at Microsoft would have raised their hand during a design session and asked "what about those people that have hundreds of projects that they want to retarget for .NET 3.5???" Pisses me off. 5 minutes into the damn thing, and I find something that is going to take at least as long to figure out how to convert myself as I've already spent complaining about it!!! Marc
-
Joergen Sigvardsson wrote:
If I were you, I'd take a copy of the solution file, then change for one project. Then compare the two solution files (or project files, or wherever the setting is). If the change is simple, then use a text editor with search/replace functionality to "just do it".
:sigh: I figured. So why is it that within 5 minutes of using the product, I find a major deficiency in it with regards to migrating VS2005 solutions to VS2008? Marc
Marc Clifton wrote:
So why is it that within 5 minutes of using the product, I find a major deficiency in it with regards to migrating VS2005 solutions to VS2008?
It's by design. It's your reason to upgrade to the next version...
-
Marc Clifton wrote:
So why is it that within 5 minutes of using the product, I find a major deficiency in it with regards to migrating VS2005 solutions to VS2008?
It's by design. It's your reason to upgrade to the next version...
-
Joergen Sigvardsson wrote:
If I were you, I'd take a copy of the solution file, then change for one project. Then compare the two solution files (or project files, or wherever the setting is). If the change is simple, then use a text editor with search/replace functionality to "just do it".
:sigh: I figured. So why is it that within 5 minutes of using the product, I find a major deficiency in it with regards to migrating VS2005 solutions to VS2008? Marc
Marc Clifton wrote:
I find a major deficiency in it with regards to migrating VS2005 solutions to VS2008?
Why do you need to change the target framework for an existing 2.0 project? Anyways, after the 'upgrade' just add the following to the first PropertyGroup in each project file.
<TargetFrameworkVersion>v3.5</TargetFrameworkVersion>
You can just add it after the 'OldToolsVersion' element or use that to grep/sed it.
xacc.ide
IronScheme a R5RS-compliant Scheme on the DLR
The rule of three: "The first time you notice something that might repeat, don't generalize it. The second time the situation occurs, develop in a similar fashion -- possibly even copy/paste -- but don't generalize yet. On the third time, look to generalize the approach." -
Marc Clifton wrote:
I find a major deficiency in it with regards to migrating VS2005 solutions to VS2008?
Why do you need to change the target framework for an existing 2.0 project? Anyways, after the 'upgrade' just add the following to the first PropertyGroup in each project file.
<TargetFrameworkVersion>v3.5</TargetFrameworkVersion>
You can just add it after the 'OldToolsVersion' element or use that to grep/sed it.
xacc.ide
IronScheme a R5RS-compliant Scheme on the DLR
The rule of three: "The first time you notice something that might repeat, don't generalize it. The second time the situation occurs, develop in a similar fashion -- possibly even copy/paste -- but don't generalize yet. On the third time, look to generalize the approach."leppie wrote:
Why do you need to change the target framework for an existing 2.0 project?
Well, because I want to test my code base with .NET 3.5. I don't care if people say it's the same thing as 2.0. I want to test it.
leppie wrote:
Anyways, after the 'upgrade' just add the following to the first PropertyGroup in each project file.
I have project files strewn across numerous directories. Why couldn't Microsoft have provided a simple way of setting the target across all projects in the solution? Marc
-
Rama Krishna Vavilala wrote:
What do you intend to achieve?
I want to compile against the latest framework so I can test it.
Rama Krishna Vavilala wrote:
As per my understanding unless you are using LINQ features there is no need to change the target?
I may use them in limited situations.
Rama Krishna Vavilala wrote:
Of course you can write a macro quickly to change target framework of all the projects in a solution.
Why TF should I write a macro?!?! Isn't this something that some intelligent person at Microsoft would have raised their hand during a design session and asked "what about those people that have hundreds of projects that they want to retarget for .NET 3.5???" Pisses me off. 5 minutes into the damn thing, and I find something that is going to take at least as long to figure out how to convert myself as I've already spent complaining about it!!! Marc
Marc Clifton wrote:
compile against the latest framework
What does it mean? If you are not using System.Core, System.Data.Linq, System.Xml.Linq what does it mean to compile against the new framework? Think this way. Someone gave you an assembly full of new stuff. Now you have lots of existing projects. You just don't need to go ahead and add the new assembly as reference to all the projects unless you are actually using it in a project. If you are using it in a project you will go ahead and add the assembly a as reference and then write code to use it. Unless you have code that uses the assembly adding a reference is of no use. The bigger issue is writing code to use the assembly not adding the reference which is insignificant. The rant here should be on the naming of ".NET Framework" version numbers. It is way too confusing. BTW The mscorlib.dll, system.dll and other assemblies you are using in teh project will automatically be upgraded to .NET 2.0 SP1 which is built into .NET 3.5. So you will automatically be testing your projects with .NET 3.5 just by building them.
Co-Author ASP.NET AJAX in Action CP Quote of the Day: It is the same Friday that blooms as a new enriching day with novelty and innovation for us every week. - Vasudevan Deepak Kumar
-
Marc Clifton wrote:
compile against the latest framework
What does it mean? If you are not using System.Core, System.Data.Linq, System.Xml.Linq what does it mean to compile against the new framework? Think this way. Someone gave you an assembly full of new stuff. Now you have lots of existing projects. You just don't need to go ahead and add the new assembly as reference to all the projects unless you are actually using it in a project. If you are using it in a project you will go ahead and add the assembly a as reference and then write code to use it. Unless you have code that uses the assembly adding a reference is of no use. The bigger issue is writing code to use the assembly not adding the reference which is insignificant. The rant here should be on the naming of ".NET Framework" version numbers. It is way too confusing. BTW The mscorlib.dll, system.dll and other assemblies you are using in teh project will automatically be upgraded to .NET 2.0 SP1 which is built into .NET 3.5. So you will automatically be testing your projects with .NET 3.5 just by building them.
Co-Author ASP.NET AJAX in Action CP Quote of the Day: It is the same Friday that blooms as a new enriching day with novelty and innovation for us every week. - Vasudevan Deepak Kumar
Rama Krishna Vavilala wrote:
What does it mean?
Let me rephrase what I meant. There's a new .NET framework out there, called 3.5. Just because Microsoft says there aren't any changes to "2.0" portion of it doesn't mean that I believe them. I want to test my code using the latest framework, even if I don't use any of the new stuff in that framework yet. Marc
-
Rama Krishna Vavilala wrote:
What does it mean?
Let me rephrase what I meant. There's a new .NET framework out there, called 3.5. Just because Microsoft says there aren't any changes to "2.0" portion of it doesn't mean that I believe them. I want to test my code using the latest framework, even if I don't use any of the new stuff in that framework yet. Marc
Then you don't need to retarget it. The new assemblies will automatically be picked up as I stated in my post. As a matter of fact .NET 3.5 is .NET 2.0 SP + bunch of stuff. Yes there have been some changes I believe to the core assemblies, but for that you don't need to retarget. Re targeting = Adding new assemblies Things you are trying to achieve does not need retargeting. Your purpose is achieved by just rebuilding the projects.
Co-Author ASP.NET AJAX in Action CP Quote of the Day: It is the same Friday that blooms as a new enriching day with novelty and innovation for us every week. - Vasudevan Deepak Kumar
-
Then you don't need to retarget it. The new assemblies will automatically be picked up as I stated in my post. As a matter of fact .NET 3.5 is .NET 2.0 SP + bunch of stuff. Yes there have been some changes I believe to the core assemblies, but for that you don't need to retarget. Re targeting = Adding new assemblies Things you are trying to achieve does not need retargeting. Your purpose is achieved by just rebuilding the projects.
Co-Author ASP.NET AJAX in Action CP Quote of the Day: It is the same Friday that blooms as a new enriching day with novelty and innovation for us every week. - Vasudevan Deepak Kumar
Hello I fully agree with your post, but there ist still one question pending, at least for me.:) VS2008 forces you to upgrade Net 2.0 to Net 2.0 SP1. Now when you are building apps against NET 2.0, with VS2008 of course, what does this mean to your target system. Does the target too have to have Net 2.0SP1 or is Net 2.0 sufficent to run the application. Is it possible to install Net 2.0 SP1 in Win2000 SP4, as it was possible with Net 2.0? I found no hint about this on MS-sites.
greetings Rainer Be as sinple as you can be; You will be astonished to see how uncomplicated and happy your life can become. --Paramahansa Yogananda
-
So, does one have to manually right-click on properties for EACH project in a solution and change the target framework to 3.5? Please tell me it isn't so. Marc
If it makes you feel any better, VS2005 has a similar quirk: When doing Compact Framework development, there's no way to change every project's target SDK (PPC 2003, WM5, etc): You have to right-click and manually retarget each project, which is then unloaded and reloaded. It's a pain.. I'm curious as to whether that still exists in VS2008. Sounds like it probably does. I get the feeling what you've discovered is going to be a big "WHOOPS!!!" on the part of Microsoft..
It has become appallingly obvious that our technology has exceeded our humanity. - Albert Einstein
-
Hello I fully agree with your post, but there ist still one question pending, at least for me.:) VS2008 forces you to upgrade Net 2.0 to Net 2.0 SP1. Now when you are building apps against NET 2.0, with VS2008 of course, what does this mean to your target system. Does the target too have to have Net 2.0SP1 or is Net 2.0 sufficent to run the application. Is it possible to install Net 2.0 SP1 in Win2000 SP4, as it was possible with Net 2.0? I found no hint about this on MS-sites.
greetings Rainer Be as sinple as you can be; You will be astonished to see how uncomplicated and happy your life can become. --Paramahansa Yogananda
Rainer Mangold wrote:
Net 2.0 sufficent to run the application.
I think this is the case. Because there have been no new methods, types etc added in SP1.
Rainer Mangold wrote:
Is it possible to install Net 2.0 SP1 in Win2000 SP4, as it was possible with Net 2.0?
No idea:( I think it might be.
Co-Author ASP.NET AJAX in Action CP Quote of the Day: It is the same Friday that blooms as a new enriching day with novelty and innovation for us every week. - Vasudevan Deepak Kumar
-
Then you don't need to retarget it. The new assemblies will automatically be picked up as I stated in my post. As a matter of fact .NET 3.5 is .NET 2.0 SP + bunch of stuff. Yes there have been some changes I believe to the core assemblies, but for that you don't need to retarget. Re targeting = Adding new assemblies Things you are trying to achieve does not need retargeting. Your purpose is achieved by just rebuilding the projects.
Co-Author ASP.NET AJAX in Action CP Quote of the Day: It is the same Friday that blooms as a new enriching day with novelty and innovation for us every week. - Vasudevan Deepak Kumar
Rama Krishna Vavilala wrote:
Things you are trying to achieve does not need retargeting. Your purpose is achieved by just rebuilding the projects.
Ahhh, ok. I'm perhaps getting a glimmer of what you're saying. But what is confusing to me is that the target framework, after converting the project, was 2.0. So I assume my application will use the 2.0 framework when it runs? Or does it run using the 3.5 framework? That would mean that the target is really just for making sure you don't write code that includes 3.x stuff when you know your destination system only has the 2.0 framework? I think I'm getting more confused! Marc
-
Rama Krishna Vavilala wrote:
Things you are trying to achieve does not need retargeting. Your purpose is achieved by just rebuilding the projects.
Ahhh, ok. I'm perhaps getting a glimmer of what you're saying. But what is confusing to me is that the target framework, after converting the project, was 2.0. So I assume my application will use the 2.0 framework when it runs? Or does it run using the 3.5 framework? That would mean that the target is really just for making sure you don't write code that includes 3.x stuff when you know your destination system only has the 2.0 framework? I think I'm getting more confused! Marc
Marc Clifton wrote:
I think I'm getting more confused!
Yes, it is very confusing. Blame the people who named the ".NET Framework"s not me.
Marc Clifton wrote:
That would mean that the target is really just for making sure you don't write code that includes 3.x stuff when you know your destination system only has the 2.0 framework?
That's it!
Co-Author ASP.NET AJAX in Action CP Quote of the Day: It is the same Friday that blooms as a new enriching day with novelty and innovation for us every week. - Vasudevan Deepak Kumar
-
So, does one have to manually right-click on properties for EACH project in a solution and change the target framework to 3.5? Please tell me it isn't so. Marc
-
You can select multiple projects and bring up a combined property sheet, right?
----
...the wind blows over it and it is gone, and its place remembers it no more...
Only for C++.
Co-Author ASP.NET AJAX in Action CP Quote of the Day: It is the same Friday that blooms as a new enriching day with novelty and innovation for us every week. - Vasudevan Deepak Kumar
-
Marc Clifton wrote:
I think I'm getting more confused!
Yes, it is very confusing. Blame the people who named the ".NET Framework"s not me.
Marc Clifton wrote:
That would mean that the target is really just for making sure you don't write code that includes 3.x stuff when you know your destination system only has the 2.0 framework?
That's it!
Co-Author ASP.NET AJAX in Action CP Quote of the Day: It is the same Friday that blooms as a new enriching day with novelty and innovation for us every week. - Vasudevan Deepak Kumar
Rama Krishna Vavilala wrote:
That's it!
Doh! Why didn't you just say so in the first place! Just kidding! Thanks so much for this clarification. Now I can sound intelligent when talking to others. :) Marc
-
Only for C++.
Co-Author ASP.NET AJAX in Action CP Quote of the Day: It is the same Friday that blooms as a new enriching day with novelty and innovation for us every week. - Vasudevan Deepak Kumar