Safely using existing vs2010 sp1 after installing vs2012/13 - visual-studio-2010

I have researched the topic and discovered that:
You can install vs2012/13 on the same machine running vs2010 sp1
You can target .NET framework 4.0 for your current projects and run them locally
The problem arises when you deploy your websites to servers that do not have fixes to bugs in .NET 4.0 that were made when installing .NET framework 4.5 on the local machine.
My question is, what is the best way I can make sure I can do the following using the same machine:
I can still run my old/current vs2010 sp1 projects without breaking locally or when deployed remotely
I can create new solutions using vs2010 sp1 targeting the .NET4.0 framework safely
I can create new solutions using vs2012/13
If I cannot have the scenario above, would using Visual Studio Online help? (I have not had much to read on Visual Studio Online) but just thought that it could be an alternative to the above?

Related

New Laptop - Any reason to install Visual Studio 2012 AND 2013?

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.

Getting error trying to deploy a sharepoint 2010 workflow package from Visual Studio 2010 in Windows 7

I'm trying to deploy a Nintex Sharepoint workflow from Visual Studio 2010, on a Windows 7 Ultimate x64 machine, running Sharepoint 2010, and I keep getting this error:
Error occurred in deployment step 'Recycle IIS Application Pool': Microsoft .NET Framework 3.5 SP1 is not installed on this system. It is required to perform this operation.
Any ideas what the problem might be or how to fix?
I kind of stumbled across the answer. I found a couple people who addressed similar issues by disabling .NET Framework 3.5.1 in Windows Features.
I turned the feature off, rebooted and it works. No more error.
I think that as the error states, you need to install Microsoft .Net Framework 3.5 SP1 on you machine. You can download it here: http://www.microsoft.com/download/en/details.aspx?id=22

Visual Studio 2010 and Moss 2007 issues

Here is the scenario: My dev environment is a Windows 2003 virtual server, MOSS2007, VS 2008, SQL2005, .net Framework 3.5, Ajax 2.0.
We're in the process of upgrading user workstations to Win 7. So I decided to install VS 2010 alongside VS2008.
When I tried to open an existing VS2008 project that has custom web parts for the MOSS, it went through the upgrade wizard but at the end it failed but I did not note what the error was. Instead, I decided to recreate the project but when adding a new sharepoint webpart to my solution I received an error stating that SharePoint must be forst installed on the server. Well lah-di-dah, it is installed!!! So now what?
Ended up uninstalling VS2010, but that is not the point. Does VS2010 requires SharePoint 2010 to work, really? Can anyone elaborate on this. Thanks.
Eric
You tried to open up a Sharepoint solution on your new Windows 7 workstation? I doubt you've got Sharepoint installed on that workstation, so the error message might be correct when it's saying Sharepoint isn't installed.
But, you can use VS2010 to do some Sharepoint 2007 development, as written here: http://social.msdn.microsoft.com/Forums/en/sharepointdevelopment/thread/bbced82a-a0e2-4a50-836a-3deb96c02de8
You still might want to have WSPBuilder installed though, even though VS2010 works pretty slick out of the box.
I've reinstalled both versions of VS and that soleved the problem. (not the most efficient method, however).

If I have Both Visual Studio 2008 and 2010, do have I have to keep both

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 :)

I have just installed VS.NET 2003 which left my newer versions (2005/2008) crippled

I had Visual Studio 2008 and 2005 installed on my machine , unfartunately i have to install VS.NET 2003 on it to work on an old project. However after the installation now my VS2008 projects are not compiling as they are unable to resolve the .NET core namespaces. I trying reinstalling .NET 3.5 and VS2008 but it still giving me the same errors while building the solution.
anybody had such experience and any tip to solve it?
strangelly VS 2005 is working fine and it means its working fine with .NET 2.0 deployments however its causing issue with ASP.NET MVC project in VS 2008 which is certainly using .NET 3.5 and yes i have given a try to reinstallation as well
rifferte is correct in that it's safest to install in the other they are released.
Probably the best thing to do at this point is to repair your Visual Studio 2008 installation. You can do this through the Control Panel -> Add Remove Programs menu. This should fix the issues you are seeing.
I think you should try the advice here:
http://channa.gunawardena.org/2008/12/installing-visual-studio-2003-after.html
Basically - you actually have to reinstall the framework outside of VS. That being said - the best advice is to always install VS editions in the order they were released.

Resources