VS2008 is it safe to let it go now?
-
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?
-
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?
aspdotnetdev wrote:
If you work with somebody else and they only have VS2008, would they be able to open your VS2010 solution?
Now, is there any solution to that? Besides loading the .csproj files separetely?
-
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 -
aspdotnetdev wrote:
If you work with somebody else and they only have VS2008, would they be able to open your VS2010 solution?
Now, is there any solution to that? Besides loading the .csproj files separetely?
Edit the solution in Notepad to make it look like a VS2008 solution file?
-
Edit the solution in Notepad to make it look like a VS2008 solution file?
aspdotnetdev wrote:
Edit the solution in Notepad to make it look like a VS2008 solution file?
That's even more unpractical than Adding csproj files individually
-
aspdotnetdev wrote:
Edit the solution in Notepad to make it look like a VS2008 solution file?
That's even more unpractical than Adding csproj files individually
Depends on the number of CSPROJ files. Also, when you add CSPROJ's to a solution, the references to other CSPROJ's in the original solution are lost, so you must then add those references again as well. Modifying the SLN file might be as simple as changing a single line. I'd probably just use WinMerge to compare a VS2008 and VS2010 SLN file to take note of the differences.
-
Depends on the number of CSPROJ files. Also, when you add CSPROJ's to a solution, the references to other CSPROJ's in the original solution are lost, so you must then add those references again as well. Modifying the SLN file might be as simple as changing a single line. I'd probably just use WinMerge to compare a VS2008 and VS2010 SLN file to take note of the differences.
Perhaps you're right. But still we'd have to compare the sln files to see what real difference there are between them (WinMerge), using which of the new features of VS 2010. I think there will be cases where either solution might make sense. The optimal solution would be that VS had an "export" feature... Humm... plugin idea?
-
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.comThat is why I develop in Virtual Machines now - my Visual Studio 6 one now rarely gets powered up, like wise VS2003, VS2005 and VS2008 still very active depending on client. This way I know that if I ever have to go back to do some fix on real old code - even if I have changed machines many times since then I can fire up a Virtual Machine and go into the project and update without faffing around.
-
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 ran across an interesting problem this week. I was trying to call a method on a BizTalk web service from my own web service on another server. I was able to generate a proxy with VS2010. But, I couldn’t successfully make a method call to it. I kept getting this error. "An error occurred while loading attribute 'XmlSerializerFormatAttribute' on method"… I wrote a test app and ran it from my machine and everything worked fine. It turns out that the proxy that VS2010 generates requires .NET Framework 3.5 SP1. Which my machine had, but the server with my web service did not have. Once I installed SP1 on the server, everything was hunckie dorie (I have no idea how to spell that). This web site finally clued me in. http://social.msdn.microsoft.com/Forums/en/wcf/thread/7d2b9c3b-61ff-443b-bee7-38d28f54c466 Scott H.
Scott H.
-
Perhaps you're right. But still we'd have to compare the sln files to see what real difference there are between them (WinMerge), using which of the new features of VS 2010. I think there will be cases where either solution might make sense. The optimal solution would be that VS had an "export" feature... Humm... plugin idea?
Fabio Franco wrote:
The optimal solution would be that VS had an "export" feature... Humm... plugin idea?
Did you already see this?
-
Fabio Franco wrote:
The optimal solution would be that VS had an "export" feature... Humm... plugin idea?
Did you already see this?
Thanks! I hadn't seen that yet, perhaps I should make an article based on that, but as a VS plugin :) If nobody has done that yet (will search a little), I will make the article.