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.comOther 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).
-
daveauld wrote:
any justification or benefit for keeping VS2008?
Only if you are doing unmanaged development.
Only if you are doing unmanaged development. I write applications for embedded systems, but find it useful to test them by compiling them with C++ in VS2005 (using PC code to simulate the I/O). Would upgrading to VS2008 or VS2010 likely be helpful, or should I stick with 2005?
-
Only if you are doing unmanaged development. I write applications for embedded systems, but find it useful to test them by compiling them with C++ in VS2005 (using PC code to simulate the I/O). Would upgrading to VS2008 or VS2010 likely be helpful, or should I stick with 2005?
I should have been more clear with my answer. Basically, if you have VS2010 you can still develop .NET 2.0/3.5/4.0 applications. But you cannot continue to develop applications which target VC Runtime 8.0/9/0/10.0. If you have existing applications which work with VC 9.0 runtime then you have to upgrade them to use VC 10.0.
-
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 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
-
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 -
I should have been more clear with my answer. Basically, if you have VS2010 you can still develop .NET 2.0/3.5/4.0 applications. But you cannot continue to develop applications which target VC Runtime 8.0/9/0/10.0. If you have existing applications which work with VC 9.0 runtime then you have to upgrade them to use VC 10.0.
Basically, if you have VS2010 you can still develop .NET 2.0/3.5/4.0 applications. But you cannot continue to develop applications which target VC Runtime 8.0/9/0/10.0. If you have existing applications which work with VC 9.0 runtime then you have to upgrade them to use VC 10.0.
So C++ console applications which just use a few API calls for sockets should be fine? Useful to know. How do VS2008 and VS2010 compare with VS2005 in terms of features and usability? Is there an "express" version of Visual C++ 2010? Is it any good?
-
Basically, if you have VS2010 you can still develop .NET 2.0/3.5/4.0 applications. But you cannot continue to develop applications which target VC Runtime 8.0/9/0/10.0. If you have existing applications which work with VC 9.0 runtime then you have to upgrade them to use VC 10.0.
So C++ console applications which just use a few API calls for sockets should be fine? Useful to know. How do VS2008 and VS2010 compare with VS2005 in terms of features and usability? Is there an "express" version of Visual C++ 2010? Is it any good?
supercat9 wrote:
So C++ console applications which just use a few API calls for sockets should be fine? Useful to know.
Even a basic app will link against a paticular version of the CRT. So, you'd still need to upgrade your app's installation routine at the very least to incorporate the new DLLs.
supercat9 wrote:
Is there an "express" version of Visual C++ 2010?
Jeremy Falcon
-
Basically, if you have VS2010 you can still develop .NET 2.0/3.5/4.0 applications. But you cannot continue to develop applications which target VC Runtime 8.0/9/0/10.0. If you have existing applications which work with VC 9.0 runtime then you have to upgrade them to use VC 10.0.
So C++ console applications which just use a few API calls for sockets should be fine? Useful to know. How do VS2008 and VS2010 compare with VS2005 in terms of features and usability? Is there an "express" version of Visual C++ 2010? Is it any good?
supercat9 wrote:
So C++ console applications which just use a few API calls for sockets should be fine?
Only if you are statically linking to the CRT or not linking to CRT at all.
-
Performance? 2010 is supposed to be slower and more bloated....
3x12=36 2x12=24 1x12=12 0x12=18
Dan Neely wrote:
supposed
???? it IS slower and bloated. We would need to replaced all of our computers if we decide to switch to VS2010.
Watched code never compiles.
-
I should have been more clear with my answer. Basically, if you have VS2010 you can still develop .NET 2.0/3.5/4.0 applications. But you cannot continue to develop applications which target VC Runtime 8.0/9/0/10.0. If you have existing applications which work with VC 9.0 runtime then you have to upgrade them to use VC 10.0.
Rama Krishna Vavilala wrote:
But you cannot continue to develop applications which target VC Runtime 8.0/9/0/10.0. If you have existing applications which work with VC 9.0 runtime then you have to upgrade them to use VC 10.0.
CRT is not .NET framework. I've never heard of anybody "targeting" any VC runtime. You simpply build what you need and then either link the CRT statically or distribute it as a DLL along with other executables.
-
Performance? 2010 is supposed to be slower and more bloated....
3x12=36 2x12=24 1x12=12 0x12=18
-
I started using it yesterday. It's quite a bit quicker on my machine. My fairly large C++ solution compiled in less than half the time as it did in VS2008. I keep hearing people say it's slower but I'm not seeing it. Cheers, Drew.
Multicore machine perhaps? I've been figuring they're trying to take advantage of the kind of machine one would expect of an early adopter, or the kind of machine someone who chronically claims they'll only touch it after service pack 2 will have after they release service pack 2.
-
Multicore machine perhaps? I've been figuring they're trying to take advantage of the kind of machine one would expect of an early adopter, or the kind of machine someone who chronically claims they'll only touch it after service pack 2 will have after they release service pack 2.
-
Rama Krishna Vavilala wrote:
But you cannot continue to develop applications which target VC Runtime 8.0/9/0/10.0. If you have existing applications which work with VC 9.0 runtime then you have to upgrade them to use VC 10.0.
CRT is not .NET framework. I've never heard of anybody "targeting" any VC runtime. You simpply build what you need and then either link the CRT statically or distribute it as a DLL along with other executables.
Nemanja Trifunovic wrote:
distribute it as a DLL along with other executables.
True and that is where you will need 2 versions of VS. Let's say you have an unmanaged application developed using VS 2008 in production. You will still need VS2008 to maintain that application. If you upgrade to VS2010 you have to re-build the application, re-build the setups and more testing. usually that means a new version of your application. But if it was purely .NET application targeting .NEt 3.5, you can afford to uninstall VS2008 and use VS2010.
-
Yup, it's a quad core. I'm wondering if the WPF parts it supposedly has benefit from the NVidia 8800GTX I have. The UI seemed really snappy to me. Cheers, Drew.
-
Dan Neely wrote:
supposed
???? it IS slower and bloated. We would need to replaced all of our computers if we decide to switch to VS2010.
Watched code never compiles.
-
Nemanja Trifunovic wrote:
distribute it as a DLL along with other executables.
True and that is where you will need 2 versions of VS. Let's say you have an unmanaged application developed using VS 2008 in production. You will still need VS2008 to maintain that application. If you upgrade to VS2010 you have to re-build the application, re-build the setups and more testing. usually that means a new version of your application. But if it was purely .NET application targeting .NEt 3.5, you can afford to uninstall VS2008 and use VS2010.
Rama Krishna Vavilala wrote:
Let's say you have an unmanaged application developed using VS 2008 in production. You will still need VS2008 to maintain that application.
That's true if your dev machine is also a build/release machine, which is in general not a good idea. Otherwise, you just make a fix on VS2010, check the change in, build with the appropriate compiler/CRT version, test and deploy.
-
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.comWhat'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
-
Rama Krishna Vavilala wrote:
Let's say you have an unmanaged application developed using VS 2008 in production. You will still need VS2008 to maintain that application.
That's true if your dev machine is also a build/release machine, which is in general not a good idea. Otherwise, you just make a fix on VS2010, check the change in, build with the appropriate compiler/CRT version, test and deploy.
As long as the proj files are same format, I guess that will work. But I prefer to keep both versions of vs.
-
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).
that is not true. One can still use XNA to develop for XBox and PC. It's true for the Visual Studio 2010 Express for Win Phone and for the CTP, but this is one thing. "XNA Game Studio and the XNA Framework are designed for cross-platform gaming scenarios with support for Windows Phone 7 Series, Xbox 360, and Windows-based PCs. This allows you to target more platforms from the same code base. Also, it allows developers to focus game design for each platform on real device differences, such as the device capabilities and experience, as opposed to writing with different frameworks for every device that is targeted"
Just an irritated, ranting son of ... an IT guy. At your trolling services