I had installed QT for some project sometime back but don't use it now(may need it later). I noticed that whenever I start Visual Studio 2010, it hogs my RAM. Is it possible to disable loading it?
It sounds like you need to use the Visual Studio Add-ins Manager to disable the Qt Visual Studio add-in.
Related
Got a big problem with the Visual Studio 2017 Installer Projects Extension for Visual Studio 2017 Professional. I added a Visual Studio Installer Setup project to a solution and set it up the way it's basically supposed to be done (Primary Output in the Application Folder and an icon in the Desktop Folder is all that was needed). Then I right-clicked on the Setup project, clicked "Build" and then I get this:
Please wait while Windows configures Microsoft Visual Studio Professional 2013.
And then it stalls indefinitely. I have to close Visual Studio in Task Manager to stop everything. What's more, I'm Visual Studio Professional 2017, not 2013. I used to have Visual Studio 2013 Ultimate, but I uninstalled it. What could possibly be causing the confusion?
It appears that you have also got Visual Studio 2013 installed, and that there is as conflict between 2013 and 2017 because that message is a Windows Installer repair of VS 2013. Something is happening during your build that requires the VS 2013 installation to be repaired. The Windows Event Log (Application) will have an MsiInstaller log entry saying which component appears to be broken. If you post that information there may be a clue to the problem. If you (for example) have manually removed anything that may belong to the VS 2013 installed product then that would cause the same kind of problem.
You have this similar problem:
Rebuilding Visual Studio Installer project, launches Visual Studio 2013 seetup
Visual Studio 2015 msi build initiates another installation
When you say it stalls indefinitely, I would expect it to ask for the Visual Studio 2013 install image so that it can repair it. If you go to Programs&Features and manually repair VS 2013 it might fix the problem.
I also had Visual Studio 2013 installed as mentioned by #PhilDW.
Navigating to Event Viewer → Windows Logs → Application I found loads of warnings:
Detection of product '{9C593464-7F2F-37B3-89F8-7E894E3B09EA}', feature 'Visual_Studio_Professional_x86_enu', component '{E3FF99AA-78B9-4A06-8A74-869E9F65E1FE}' failed. The resource 'C:\WINDOWS\Microsoft.NET\Framework\URTInstallPath_GAC\' does not exist.
The key here being that the folder C:\WINDOWS\Microsoft.NET\Framework\URTInstallPath_GAC\ did not exist thanks to an answer in the first link provided by #PhilDW.
Created the missing final folder URTInstallPath_GAC in the path mentioned and the installers now build really fast whereas before they used to take forever (sometimes literally!).
I recently started a new job, and got a machine with Visual Studio 2013 Proffesional installed. This would be great, except the colleague that I'm working with is using Visual Studio 2010. As far as I know, there is no way to work on the same project (or solution), without having quite a lot of issues, is this correct?
And if so, is it still possible to download Visual Studio 2010 (from a reliable source)? I cannot seem to find it anywhere in my MSDN subscriber downloads. All I can find is a stuff like service packs, tools, etc. Did they terminate the support of it?
You work on visual studio 2013 but there are option to select which version of visual studio you want select 2010 and run your project.
You should be able to open Visual Studio 2013 solutions in 2010, if you install Visual Studio 2010 SP1. There is a possibility that some project types won't be supported, but the solution should open.
I have Visual studio 2012 Professional already installed on my machine. I installed Visual studio Ultimate. I am not seeing Intellitrace windows or in IntelliTrace options in Tools-->Options in VS 2013.
I know, IntelliTrace is not available with Professional version. Am I missing anything?
What you are doing here should be supported. There are a couple of things that you can do to trouble shoot the issue.
1) Double check that you are actually launching Visual Studio 2013. I know that this sounds silly, but different versions of Windows will set up file or project associations differently. So, though you have installed 2013, it is possible that your regular workflow is actually still launching 2012. Check the splash screen and/or the Help > About dialog.
2) Reset Visual Studio. It is possible that something got corrupted in your extensions cache during your installation that is preventing Visual Studio from recognizing IntelliTrace. This should be relatively simple:
Launch the "Developer Command Prompt For Visual Studio 2013"
cd to [Program files x86]\Microsoft Visual Studio 2013
Execute the command "devenv /updateconfiguration" followed by "devenv /setup"
The last step may take a number of minutes depending on your system configuration. After it is finished, relaunch Visual Studio to see if IntelliTrace is available.
I am writing a Visual Studio template wizard. And to debug it I have it start a new instance of Visual Studio 2010.
My Visual Studio 2010 takes a good while to start up. I believe that this is due the the add-ins and extensions that I have installed for visual studio.
I would rather not go disable them all (I really like them). So I was hoping there was a way to disable them via the command line.
Just run a clean Visual Studio instance.
Is there a way to do that?
Try safemode
devenv.exe /safemode
which
Starts Visual Studio in safe mode, and loads only the default environment and services, and shipped versions of third-party packages.
See http://msdn.microsoft.com/en-us/library/xee0c8y7.aspx
I want to install Visual Studio 2005 on my machine which already has Visual Studio 2010?
Please help me out.
Bharat
It can easily be done -- My other laptop has VS 2005, 2008, and 2010 all on the same drive. The two versions shouldn't interfere with each other. Visual Studio even has a "version selector" that gets registered as the handler for project and solution files, and IIRC it should launch the correct version of VS for whatever project you're in at the time. But even if it doesn't, you can always right-click and "Open with...".