I recently downloaded VS 2010 trial, the new version is more easy to use.
I have VS 2008 installed, If i decide to use VS 2010 in the future, do I still have to keep VS 2008? Is there any compatibility issue with it?
You would need to keep VS2008 installed if you target Windows CE (via Compact Framework, native smart device projects, etc.)
http://msdn.microsoft.com/en-us/library/sa69he4t.aspx
Also if you want to write native applications that run on versions of Windows before XP SP3 and Server 2003 SP2, this is no longer possible with VC++ 2010. The same applies to managed code written for the .NET Framework 4.0, but you can still use Framework 3.5 with VS2010 for projects with managed code only.
And Intellisense for C++/CLI code is gone (MS promises to remedy that in the future, whether a service pack or the next version I cannot say).
If you open a VS 2008 solution or a project in VS 2010 it will be converted to VS 2010 and you will not be able to open it in VS 2008.
If that is not a problem then you don´t have to keep VS 2008, unless you are using a addin or some other third party application with VS 2008 that is not compatible with VS 2010.
Edit:
Look at Ben Voigt´s answer for information for which version have support for different platforms.
VS2010 allows you to specify the target framework that you'd like to develop on. There should be no reason to keep VS2008 installed unless you've become accustom to some handy plugins :)
Related
I've just been given a new work laptop and have an MSDN subscription. My old laptop had VS 2008, 2010 and 2012. I'd rather not install all of these again if I can avoid it. My main question here is whether there any reason to install VS 2012 if I have access to VS 2013? I believe Projects & Solutions are compatible, what other reasons might there be for installing VS 2012 (and for that matter VS 2010) again? If I have an MVC 3 app created with VS2010, will it be possible to open and work with that in VS2013 without having to "upgrade" the project type?
It really depends on what kind of projects you are working on. Each new releases of VS in fact remove certain features.
http://msdn.microsoft.com/en-us/library/vstudio/hh266747.aspx
ASP.NET MVC 3 is not supported by VS2013.
Lex' answer is pretty good. I'd also like to add that if you are using C++/CLI, upgrading to Visual Studio 2013 will force you to target .NET 4.5, which might not at all be desirable if your users only have .NET 4.0 etc.
You can still target the older frameworks, by letting VS2013 use the older "Platform Toolset" from e.g. VS2010 or VS2012, but this will force you to have either one of these installed. I am using this exact scenario (VS2010 + VS2013) and it works quite well. (I have only VS2010 and 2013, not 2012 in that specific virtual machine.)
Update: Here is a MSDN page which backs up my statement about C++/CLI, just for the reference.
I'm trying to set up some new developers to make apps for the Okuma control using the Okuma API and SDK. What environment should they use? I tried installing Visual Studio Express 2012 but it keeps giving an error looking for files during install. Also, what language should they use so they can work with the Okuma API?
The Okuma API is written using .NET 4.0 so you really have several options.
Normally I'd say Visual Studio express 2012 for desktop is best but I've seen problems putting it on Windows XP.
If you're using windows XP and aren't ready to invest in a full version of Visual Studio yet, I'd recommend Visual C# Express 2010. If you're more familiar with VB and don't want to switch, do the VB express verison.
All these (and the professional version) are available from
www.microsoft.com/visualstudio/eng#downloads
VS 2019 community edition is currently working fine for me doing this. I just have to choose which .net framework in the project settings. That was not listed in the prior answer in case anyone comes across this in the future.
I have a old web application developed in .NET 1.0. How can I do some minor changes in it? What Visual Studio do I need and how do I obtain it? Or can I develop in some other tool?
Thanks in advance!
It was called VisualStudio.NET, followed by Visual Studio 2003 (also known as version 7.1).
I don't think this is available anymore, unless you have a pro MSDN subscription or above.
Visual Studio 2005/2008/2010 cannot be used for this, nor can mono-develop, but you might be able to use the version of SharpDevelop that supports 1.1.
You'd need Visual Studio 2002, it targeted .NET 1.0. That edition didn't last long, Visual Studio 2003 and .NET 1.1 quickly followed. Your project should have good odds opening and running properly on that edition. Odds get lower once you move to VS 2005/8 and .NET 2.0+
If you don't have VS2002 then you can obtain a license through an MSDN Library subscription. An auction site like Ebay is a cheaper alternative.
It was originally called Visual Studio.NET but later on also got referred to as Visual Studio 2002.
I looked it up and apparently you can still download it if you have an MSDN subscription.
You can use VS 2005, VS 2003, or VS 2002. I think the 2002 edition was called VS.NET.
From http://weblogs.asp.net/scottgu/archive/2007/06/20/vs-2008-multi-targeting-support.aspx
What about .NET 1.0 and 1.1?
Unfortunately the VS 2008 multi-targeting support only works with .NET 2.0, .NET 3.0 and .NET 3.5 - and not against older versions of the framework. The reason for this is that there were significant CLR engine changes between .NET 1.x and 2.x that make debugging very difficult to support. In the end the costing of the work to support that was so large and impacted so many parts of Visual Studio that we weren't able to add 1.1 support in this release.
VS 2008 does run side-by-side, though, with VS 2005, VS 2003, and VS 2002. So it is definitely possible to continue targeting .NET 1.1 projects using VS 2003 on the same machine as VS 2008.
Take a back up of your project.
Try to down load visual studio express 2008 version and open the project. you will have an option to convert. Once converted download the latest visual studio express and then convert into the latest version.
BTW Visual stuido express is FREE
Note:
Some of the methods may not be supported or droped. you need to recode them or replace them.
Now Visual Studio 2010 is out can I use Visual Studio 2010 without breaking my 2008 apps? Can I still compile to .Net 2.0 etc?
Thanks
Steven
Yes, you can still target framework 2.0 in VS2010. And you can also run VS2008 alongside VS2010.
Basically, yes, but there are a few things that get changed, for instance:
Testing projects always get converted to .NET 4.0
Project files get stored in "VS 2010" format.
So downgrading back to VS 2008 is not directly possible (in 99% of all cases it's still not a problem by hand-editing the files, takes just a few seconds).
However, usually, this is not an issue though. Your deployment capabilities are not limited by that. You can still target any framework.
Additionally, I found that running VS 2008 alongside 2010 made no problems at all. Including 2008 projects in a 2010 solution works fine and does not change the project file. It's very easy to slowly transmit to the new version step-by-step.
What reasons are there for continuing to run Visual Studio 2005 when 2008 is available?
I work on a project where the environment is dictated to be Visual Studio 2005. Are there good technical reasons for this? Can I use Visual Studio 2008 and build an app that is 100% indistinguishable from the same app build with Visual Studio 2005?
I think there are two questions here
Can I use VS2008 to create apps compatible with VS2005
Generally speaking the answer is yes. I do this frequently with several internal and external hobby projects with great success. You may encounter an odd ball tooling issue but so far none has cropped up for me.
Is there any reason not to use VS2008 over VS2005
The best reason I can think of is a large developer environment. Once you make the switch to using VS2008, it will upgrade all of the projects in your solution to the new format. This will no longer be usable for anyone using VS2005. They will be forced to upgrade or maintain parrallel versions of the project file. In general, I find it's best to upgrade in groups rather than individuals.
We are currently migrating from 2005 to 2008. If you open and save a project while in VS2008, you will not be able to open that solution/project in VS2005 (at least we couldn't find a way easily). If the rest of your team is still in 2005, you should stay there. You CAN, however set up a project in 2008 and keep it compatible with 2005... as long as everyone opening it is using 2008. You keep the .NET version at 2.5, and don't convert most of the stuff that it wants you to convert.
The only time you CAN'T migrate to 2008 is if you are using a report project and SQL Server 2005. VS2008 will only let you integrate a report project with SQL Server 2008. What did we do?
We migrated to 2008 and all the Team Server stuff, except for the database and reporting. Those we kept on 2005, and so I end up having to open both versions on a daily basis... but that's why they pay me the (somewhat??) big bucks!
Not really, the new version of Visual Studio has the compilers for the new language versions and all the libraries for .NET 3.5. Since they all target the 2.0 CLR and Visual Studio 2008 allows you to target previous versions of the framework I don't see any reason to stick with 2005.
The obvious answer is: No license for Visual Studio 2008.
My company is "saving money" but not upgrading...
One reason might be interaction with existing products.
I write code for AutoCAD in C#.
They (Autodesk) "officially" support VS 2005 but I've been using 2008 since...well 2008.