VS2008 is it safe to let it go now?
-
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.