VS2008 is it safe to let it go now?
-
and then there was SolutionConverter[^] which looks interesting; I haven't tried it though. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read formatted code with indentation, so please use PRE tags for code snippets.
I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).
or you can use [^](http://code.google.com/p/gyp/wiki/GypUserDocumentation”>GYP</a>[<a href= "New Window")] :) Solution converter is interesting.
-
or you can use [^](http://code.google.com/p/gyp/wiki/GypUserDocumentation”>GYP</a>[<a href= "New Window")] :) Solution converter is interesting.
are you referring to gStudio? :laugh: the link seems slightly dammaged, a bad omen. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read formatted code with indentation, so please use PRE tags for code snippets.
I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).
modified on Friday, May 14, 2010 6:34 PM
-
As long as the proj files are same format, I guess that will work. But I prefer to keep both versions of vs.
Rama Krishna Vavilala wrote:
As long as the proj files are same format
Which they wouldn't be because they contain version info, so it would break it. I mean if you really, really wanted to you can use nmake to get around it - and sometimes automated builds do - but that's just being weird. :)
Jeremy Falcon
-
are you referring to gStudio? :laugh: the link seems slightly dammaged, a bad omen. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read formatted code with indentation, so please use PRE tags for code snippets.
I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).
modified on Friday, May 14, 2010 6:34 PM
I was referring to gyp. http://code.google.com/p/gyp/[^]
-
On my laptop and my main PC i have both VS2008 and VS2010 today i took a VS2008 project folder and copied to VS2010 project folder and it did an inplace conversion without any issues. As both these IDE's are multi-targetting, is there any justification or benefit for keeping VS2008?
Dave Don't forget to rate messages!
Find Me On: Web|Facebook|Twitter|LinkedIn
Waving? dave.m.auld[at]googlewave.comI am not sure it is safe to uninstall visual C++ 6 as I have 100s of thousands of lines of code in projects that will only compile under that version. Same with 2003. As for 2005 and above porting will probably be simpler for multiple reasons. One is that I use CMake now for my project file generation and do not put any .sln or .vcproj files in my source control at all.
John
modified on Friday, May 14, 2010 11:21 PM
-
On my laptop and my main PC i have both VS2008 and VS2010 today i took a VS2008 project folder and copied to VS2010 project folder and it did an inplace conversion without any issues. As both these IDE's are multi-targetting, is there any justification or benefit for keeping VS2008?
Dave Don't forget to rate messages!
Find Me On: Web|Facebook|Twitter|LinkedIn
Waving? dave.m.auld[at]googlewave.com -
On my laptop and my main PC i have both VS2008 and VS2010 today i took a VS2008 project folder and copied to VS2010 project folder and it did an inplace conversion without any issues. As both these IDE's are multi-targetting, is there any justification or benefit for keeping VS2008?
Dave Don't forget to rate messages!
Find Me On: Web|Facebook|Twitter|LinkedIn
Waving? dave.m.auld[at]googlewave.com -
daveauld wrote:
is there any justification or benefit for keeping VS2008
Some plugins might only work for VS2008. If you work with somebody else and they only have VS2008, would they be able to open your VS2010 solution?
-
daveauld wrote:
any justification or benefit for keeping VS2008?
Only if you are doing unmanaged development.
-
Other than VS2010 wasn't much of an improvement? If you're interested in XNA Game Studio then you wont be able to develop for anything other than Windows 7 Mobile as the 4.0 CTP will integrate into VS2010 but only allows building for mobile platforms (3.1 is the one to use an only integrates into 2005 and 2008).
-
I personally get rid of the older VS version as soon as the new one comes up. SO IMHO, there is no point keeping VS 2008 if you have VS 2010.
-
I mean, GB are at a premium these days. I am not going to delete VS2008 but I am not going to install it when I get my new system in August.
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. A man said to the universe: "Sir I exist!" "However," replied the universe, "The fact has not created in me A sense of obligation." --Stephen Crane
-
What's scary is that you used the word "safe" in the same sentence as "VS". You're a brave soul.
Everything makes sense in someone's mind
-
Performance? 2010 is supposed to be slower and more bloated....
3x12=36 2x12=24 1x12=12 0x12=18
-
Why do you want to let it go? They can run side by side and IMO, you never know when you might need it.
-
On my laptop and my main PC i have both VS2008 and VS2010 today i took a VS2008 project folder and copied to VS2010 project folder and it did an inplace conversion without any issues. As both these IDE's are multi-targetting, is there any justification or benefit for keeping VS2008?
Dave Don't forget to rate messages!
Find Me On: Web|Facebook|Twitter|LinkedIn
Waving? dave.m.auld[at]googlewave.comOur policy has always been to maintain a product with the tool chain used to develop it originally. For that reason, we still have VS2003 installed, as most of our legacy applications were developed using it. There is simply too much regression testing required when you update tools. Compiler changes typically require significant source changes. For example, our library of TCP/IP socket communications, threading, and other tools were ported from VS2003 to VS2008 for a new product. This took us a month, along with a fair amount of bug fixes and tweaks since then. Porting our entire legacy product line wouldn't generate any customer benefit, and would entail significant risk.
Software Zen:
delete this;
Fold With Us![^] -
On my laptop and my main PC i have both VS2008 and VS2010 today i took a VS2008 project folder and copied to VS2010 project folder and it did an inplace conversion without any issues. As both these IDE's are multi-targetting, is there any justification or benefit for keeping VS2008?
Dave Don't forget to rate messages!
Find Me On: Web|Facebook|Twitter|LinkedIn
Waving? dave.m.auld[at]googlewave.comIf you work on Smart Device projects (compact framework/CE apps) then absolutely... they seem to be completely MIA in 2010 as far as I can tell. Pages found via Google suggest these projects and CF have been dropped in favour of the Win 7 Phone SDK (not yet released), which would be fine except we have line of business applications running on barcode scanners, thin clients and other hardware with CE installed that aren't phones and certainly aren't Win Phone 7. The same pages from Google also seem to indicate that if the Smart Device projects are a requirement for you, stick to VS2008 :( Opening a Smart Device .csproj file in VS2010 just says the project type isn't supported, and it won't update it :( Of course, if you don't have that issue and all your add-in's etc. run ok, then it should be safe to move to 2010.
-
On my laptop and my main PC i have both VS2008 and VS2010 today i took a VS2008 project folder and copied to VS2010 project folder and it did an inplace conversion without any issues. As both these IDE's are multi-targetting, is there any justification or benefit for keeping VS2008?
Dave Don't forget to rate messages!
Find Me On: Web|Facebook|Twitter|LinkedIn
Waving? dave.m.auld[at]googlewave.comIt depends on what you're using it for. For example VS2010 can't be used to work on BizTalk 2009 at present. Also, if you're working in a team with people using previous versions, it's best to keep everyone on the same version; so either all upgrade together, or all stick to 2008. I think that OOTB visual studio, being used for standard PODN (plain old dot net) development, should be fine though. You could just keep the installs for VS2008, or keep a virtual machine image with it on, to call up in case you hit issues down the line, then you're pretty much safe whatever.
-
daveauld wrote:
is there any justification or benefit for keeping VS2008
Some plugins might only work for VS2008. If you work with somebody else and they only have VS2008, would they be able to open your VS2010 solution?