My laptop had an install error with Vista Ultimate and now it does not let me run Visual Studio. I was able to install Visual Studio 2008 on my HP TouchSmart without a problem and now I use it on there. I want to be able to travel though. So I was wondering if I take the folder in which Visual Studio was installed and put it on my external hard drive and just run it off of there. Is this possible? I've managed to do it with other programs before.
No this will not work with Visual Studio. You're essentially asking if Visual Studio is xcopy deployable. It unfortunately is not. It relies on many items which are not simply a part of the install folder including ...
Registry Keys
Certain versions of the CLR being installed
Supporting programs and libraries
And many, many other items.
As others have said, because of the dependencies it is not xcopy deployable. Maybe Virtual PC is the answer to your problems.
You can install VS 2008 on some other drive/older in your computer. Bu VS 2008 needs to run some DLL or other files to run in the OS. So you can not install it.
There are many pre-requisites that are installed with VS 2008, so I think that it's not a good idea.
Related
I want to install vsiual studio as i have also running same pc visual studio-2013 professional edition.I am seeking help for finding is there any problem to install this.
Yes, it's possible, and no, you don't have to do anything special; the two IDEs are entirely separate, you just install each of them. Of course, the Visual Basic 6 IDE has been end-of-lifed for years now.
Actually the question is not silly. Installing VB6 used to break previously installed versions of Visual Studio and usually required them to be reinstalled (and depending on the direction of the wind might require some registry hacking as well). Since VS2010 you can safely install VB6 after Visual Studio.
I have an issue that I am using Visual Studio 2005 on my system with Windows XP SP1 as an operating system. Now I want to install Visual Studio 2010 with SP3 without uninstalling VS2005.
My question is, will my project in VS2005 still work properly? Can I work in both versions without any conflicting issues?
This should be possible. According to the MSDN Documentation(Installing Visual Studio Versions Side-by-Side) you can install them side by side.
You can't however open a VS2010 project in VS2005. So you need to keep your work strictly separated between those versions if you want to be able to open your project in VS2005.
I have VS2005, 2008 and 2010 all running on the same Vista box with no conflicts. As long as you don't upgrade your 2005 projects (by choosing to open them in VS2010 and accepting the upgrade prompt) you'll be fine.
The big question here is: will VS2010 actually run on XP SP1?
Hello I have created a DLL file using visual C++ 2010, that runs a C script that i have written.
I have then created a user interface using visual C# 2010 and linked everything together.
On my machine the resulting exe application runs perfectly.
However when i try to put the folder, containing BOTH the exe and the dll, on other computers.. it runs on some computers, but on others it does not.
the error i receive has to do with "Cant find dll file or assembly".
All computers have windows 7 64bit installed.
My question is: Is there a requirement for the application to run? (files or something that should be installed on all machines???)
I have noticed the following (after alot of looking) that:
the computers that run the application HAVE visual studio 2010 installed
the computers that do not run the application DO NOT have visual studio 2010 but have visual studio 2008 installed..
all computers have .NET framework 4.5 installed.
Do you think the visual studio has anything to do with this?!!? isnt the point having a stand alone application is to make the app run on any machine?
Is there a way to fix it so that the app will run on any computer regarding having visual installed or not?
thank you all..
You can use Dependency Walker to check what dll the program can't find.
Just load the .exe into the program.
You might also find that you will need to install the Visual Studio 2010 Redistributable on those computers that you are deploying to.
I installed Visual Studio 2010 Premium on my Windows 7 workstation. After loading a test C++ project, I noticed that it could not locate iostream. I took a look in C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include and noticed that only two files exist here, srv.h and wmiatlprov.h
I installed the VS2010 product on a test virtual machine, and this directory (...\VC\include) is filled with the usual collection of folders and headers (the materials you'd expect to find in the includes directory.)
I have taken the following steps to rectify the missing headers on the problem workstation:
Verified that I have no A/V software active (I am using MS Security Essentials, realtime is disabled)
Uninstalled Visual Studio 2010 Premium and all other sub-products from Programs & Features
Ran the VS2010 Uninstall Tool with the /full and /netfx parameters
Deleted the Visual Studio 10.0 directories from both Program Files and Program Files (x86)
Reinstalled Visual Studio 2010 from a freshly downloaded ISO from MSDN.
I also completed the above steps, but used a different edition for the reinstall, VS2010 Professional.
So far, nothing above has been able to produce an installed Visual Studio 2010 product with all of the C++ headers installed on my workstation.
Ideas?
The solution to this problem is as follows. It is based on the solution given in
http://connect.microsoft.com/VisualStudio/feedback/details/774158/re-installed-visual-studio-2010-and-c-standard-headers-are-missing
Uninstall Visual Studio 2010.
Uninstall Visual Studio 2010 SP1 (despite the warning it gives).
Open Registry Editor (regedit).
Search for keys named PaddedVersion
Remove any parent keys VisualStudio\10.0\VC\Libraries, or similar (note the version number 10.0, which corresponds to 2010). Delete all of these registry paths. The search for the PaddedVersion key is just to ease up this search.
Install Visual Studio 2010.
Install Visual Studio 2010 SP1.
This solution may not be minimal, but it works for me. Hopefully others can confirm. The important difference here is that it is not just the HKEY_LOCAL_MACHINE from which the registry path must be deleted, as indicated in the link above.
While doing some research on this topic it seems like no matter how you uninstall Visual Studio there are always pieces left behind.
Two options to consider.
Option 1
Install VS 2010 on virtual machine.
Zip needed files from your virtual machine.
Copy and unzip them over to the workstation.
Option 2
Format hard drive.
Install fresh copy of Windows 7.
Install fresh copy VS 2010.
The Visual Studio installer is a fickle beast, to put it mildly. The generic diagnostic is that your registry is dirty, having a record of a sub-component of VS installed while it is not actually present anymore. There are a lot of sub-components and an enormous number of registry entries that keep track of their install state and their config. Finding such a dirty key back is a serious needle-in-a-haystack problem.
This kind of registry damage is very common if you ever had a beta or RC edition installed. I never had a beta version that didn't give me an enormous problem getting the RTM version installed. The VS2010 beta went particularly badly for me, albeit that I shot my foot badly by updating to Windows7 without uninstalling the beta. A gigantic mess, to put it mildly. You can expect similar kind of upheaval of you ever had an un/install that didn't complete. And of course registry damage is always around to turn this into misery.
The problem is quite common, there are Visual Studio cleanup tools around that aim to purge the registry after something like this happened. For VS2010 there are actually several. Google "vs2010 uninstall utility" to find them. No idea if they are different someway, no reason I can think of to not just run them all.
Chips are seriously down when that still doesn't fix the problem. Only thing left is to dig through the dd*.txt files that are left in the TEMP directory after an install. They contain a detailed trace of the installer's decisions. Beware that you'll drown in the amount of data.
I tried several rounds of uninstalling and reinstalling. The hack that finally worked was to copy the entire contents of the VC folder from a machine with a working VS 2010 installation. You probably don't need to copy all of these , but I was missing 3000+ files in include, lib, and other folders within VC.
I ran into this problem on Windows 8.1 when the VS 2010 Web installer failed to install correctly the first time. I followed Kaba's steps above with a slight difference and it solved the problem for me (so kudos to Kaba). The difference is that I deleted all the “VisualStudio\10.0” keys and all its sub-keys, as well as the “VisualStudio\10.0_Config” and sub-keys.
The solution at http://connect.microsoft.com/VisualStudio/feedback/details/774158/re-installed-visual-studio-2010-and-c-standard-headers-are-missing not worked for me.
After Uninstall Visual Studio 2010 and SP1, I used a registry cleaner software CCleaner and installed again. It fixed.
I need to have Visual Studio 6 installed on a machine that already has Visual Studio 2010 Professional installed.
Can this be done without overwriting libraries, registry settings, etc., or should I go the longer route and set up a VM with Visual Studio 6 installed there?
Can Visual Studio 2010 co-exist with Visual Studio 6?
I know from experience that you can do the reverse - install VS6.0 and then 2003, 2008, and 2010, and have them all function. In this case, if 2010 is already installed, the likely worst case scenario is having to reinstall 2010. More than likely though, it will work out of the box. Unless you already have a VM set up, it will almost certainly be easier just to install VS 6.0.
Of course, if this is a matter of making a change to a specific legacy app, then you may want to set up the VM anyway for the ease of handing the project off to the next developer who has to work on that app.
Here's a question asked by someone using a similar setup, explaining a known issue and a workaround. i.e. it doesn't seem to be without its dificulties, but is not an impossibility.
There's no problem installing different versions of Visual Studio side by side.