I wonder if They can work perfectly together...
Yes VS'08 and VS'05 will work nicely when installed on the same machine.
Now, if only they made the .NET 2.0 support in VS'08 use the same solution/project file version number as VS'05 so you could easily move back and forth VS versions with the same project without modification.
The simple answer is yes - I have both installed on the machine I'm replying to this question from. :=)
I have both running on my machine and all seems to be fine after 2 weeks of use...
Yes, they work well together. Refer to Installing Visual Studio Versions Side-by-Side on MSDN for more information.
You may need to install VS2005 before VS2008 though, or you're file associations may end up not working correctly.
Related
Trying to run an old project in Visual Studio 2015. It was created in 2012 or 2013, I cannot remember which. I have uninstalled both programs as I was running out of space, and i think that is what caused this. I get the following options:
And I do not want to change the target, so clicking on the second option brings me to https://www.microsoft.com/net/targeting which I can't seem to find anything there that remedies the situation. Is there a way around this without reinstalling the old version of Visual Studio again? Will that even fix my problem? Thank you.
Just Reinstall Visual Studio. When you uninstalled previous version it caused this problem.
You could try doing a repair reinstall of Visual Studio 2015.
Another point to consider is that Windows 7 (the oldest version of Windows still supported by Microsoft) includes a Windows Update for the .NET Framework v4.6.1 categorized as an "Important" update. I have not confirmed with Windows 8, but I suspect it, too, includes a similar update. Windows 10 comes with .NET 4.6 to start with. That means that any up-to-date supported machine today will be able to run apps targeting any .NET version up to and including 4.6. I recognize that there may be other reasons to continue targeting an older .NET version, but I bring this up just in case the concern is support on client workstations.
I am learning archicad and trying to open an existing example from API Development Kit in VS Express C++ 2013. I have installed SDK 7.1. in order to 64 development as VS Express doesn't run it by default. I am having trouble to run the example.
However, I installed all the necessary components and programs. This error window pops up all the time I try to run. I really have no clue how to make an archicad sample project run in VS C++ Express 2013.
The third line in Russian is translated as: "Impossible to find the designated folder".
I copied the API DevKit folder into the VS Express folder, doesn't help.
Please, help if someone faced such a problem or does all this stuff.
P.S. I need to run ArchiCAD in VS C++ Express.
This is the print screen:
As a former Archicad API developer, I would definitely recommend you to use Visual Studio 2005 Express.This specific version (assuming you are developing for AC12 and above), is compatible with the API (I developed for AC13 and AC15, it worked fine). That is also recommended by Graphisoft itself.
for further information:
http://www.archicadwiki.com/Developer/Getting%20Started%20with%20the%20API%20DevKit#Getting_Started_with_the_API_DevKit
You have to check the encoding of APIdefs_Automate.h. If it is ANSI, it will fail. The encoding must be UTF-8.
For older archicad projects you had to use vs2010. For the new 21 they upgraded to vs2015. To use vs2015 in older projects you have to have vs2010 installed to use it's v100 platform toolset. Then when you open an older project with the new visual studio, it asks for upgrading the project, here say no and you are good to go.
I currently have Visual Studio v2003, v2005, v2008 installed on my system. Things work fine...no issues.
I now have to install Visual Studio 2010 on my system and just wanted to know if anyone has a setup like mine or knows if there are any potential issues with so many versions existing on a system.
Really don't have a choice to remove older versions as we have a lot of legacy products written in these old versions and we are not upgrading them to new versions, only doing bug fixes on them.
Any ideas?
Thanks!
VS2010 supports targeting on multiple versions of .NET Framework (i.e. 2.0 or later), which mean it is designed to support the projects that were built with VS2005/VS2008 so-called backward-compatibility.
So I think no conflict here between these versions,
I've found a nice Myths and facts about VS 2005/2008/2010, check out this link here: http://msdn.microsoft.com/en-gb/ee679805.aspx
It should work.
I have vs2003, vs2008 and vs2010 installed and I see no issue (but vs2010 is not yet used for production code).
M.
All these versions of Visual Studio are independent.
You should have no problem (other than lack of disk space!) installing VS2010 as well.
Just make sure you install the service pack as well.
They cohabitate fine, I have a similar setup myself.
You should at least push for migrating away from 2003 and 2005 though, they use some pretty old technology, and pretty much everyone these days has .net 3.5 on their systems.
If you are able to use VS 2010 I would highly recommend you do for all new projects - even if you have to target an earlier version of .NET framework.
Keep the old versions of VS installed only for maintenance of projects that cannot be migrated to VS 2010 version.
By the way, the migration to VS 2010 is often very trivial and well worth an hour or two of effort!
I need both of them on one computer, first for educational purposes and second for work. Will there be compability problems?
Yes. I have both of them installed side by side without any issues
They should work together fine. Just be sure to install them in order from oldest to newest. See this MSDN article for details.
It should work fine, I have both installed on my current machine.
But just as an fyi, 2008 wasn't designed for Windows Vista/7, so it might throw up a warning or two when installing.
Aye, it's possible. They install to different directories, and operate on different files, so no problem should be caused by having them both installed. (I have Visual Basic 05 and 08 on the same machine)
I am too paranoid to install VS2010 Beta 2 on my production machine beside VS2008 without hearing from people who have already took the plunge. I know MS says it's OK, but that does not necessarily mean it will work.
Has anyone successfully installed VS2010 Beta 2 (preferably Ultimate edition) on their production machine with no negative consequences?
If you're that paranoid (and perhaps reasonably so!), have you thought of running it up in a virtual machine ? You can then point it to the same source repository, and be confident that the two won't interfere.
I have installed VS2010 beta 2 in my machine, together with VS2008, and it seems to work fine. There were two compelling reasons for me to start using it right now, both related to Silverlight: unit testing and visual designer.
Take a look at some of the list of known issues in VS 2010 beta 2.
I have installed it to a machine with VS 2008 on it that I don't care about. :)
Looking at the "correct" uninstall procedure from that link above makes me think that not putting it on a production box is a good idea... Going from that beta to the next one is going to be a PITA.
And whoever said they are WPF/Winform it won't conflict is crazy. .Net 4 installs side by side, yes. But there are policy files and binding redirects installed for all editions on your box because VS 2010 can also build / debug / test .Net 2/3/3.5 assemblies. You are touching every .Net runtime on your box when you install VS 2010 (like it or not).
It's working for me; I haven't seen any problems so far (admittedly in, like, one day).
That said, I'd be a lot more cautious if we didn't have a separate build server for our production builds.
Since it's in Beta, I would not install it on a production box; not even in your daily development machine. The best solution is a virtual machine, which is the way I always try beta software.
VS2010 beta 1 worked perfectly alongside VS2005 and VS2008 on two PCs for me. (One XP, one Vista)
It also uninstalled cleanly in both cases.
This is no guarantee of Beta2 working perfectly of course, but you should be ok. Generally the advice is: don't install Beta visual studio releases on development machines - use a virtual PC or a PC you don't mind reinstalling the OS on.
I have a parallel install of VS 2008 and VS 2010 beta 2. The only negative consequence is that some Microsoft DLLS (Microsoft.Test...) that is part of the unittest framework on both vs2008 and vs2010 needs to be referenced by version in the vs.net 2008 projects. Otherwise vs2008 may just pick the vs2010 reference by default and you get compilation errors.