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.
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 got the Visual Studio Professional 2015 Update 3 and launched the executable (vs2015.3.exe) while Visual Studio was still running. I got the following "Setup warning" but thought that a computer restart was fine as long as I could work during the update.
Please close visual studio now to reduce the chance that a computer
restart will be required later
Visual Studio immediately started acting strange, loosing Intellisense among others. I decided to restart Visual Studio and was then met with the error:
Cannot run when setup is in progress
I then canceled the update and thought that I could install this update during the night instead. When I opened Visual Studio again and tried to load a project I got the following error:
Project '' could not be opened because the Visual C# 2015 compiler
could not be created. Please re-install Visual Studio.
I then opened Update 3 executable again to complete the update. I was met with this feature list and could not do anything:
Restarted the computer but was met with the same dialog. I then opened Visual Studio again and this time the project loaded but without Intellisense. Restarted Visual Studio and now the project would not load at all. I then deleted the content of these 2 folders and ran devenv /resetsettings
C:\Users\%USERNAME%\AppData\Roaming\Microsoft\VisualStudio\
C:\Users\%USERNAME%\AppData\Local\Microsoft\VisualStudio\14.0\ComponentModelCache
I could now open the Visual Studio project normally again but I still could not get features when running the Update 3 executable. Is there anything else I can do or do I need to reinstall Visual Studio completely? I think it is really bad that the warning Microsoft gives is that a computer restart might be required when obviously the program cannot run in the background while updating.
Solved it by going to Control panel -> Programs and Features -> Microsoft Visual Studio Professional 2015 with Updates. Click "Change" and then select "Repair".
I have problem with my Visual studio 2013. When I'm trying to create even a simple console application,VS hangs and after a while the message 'Visual studio is busy: Microsoft Visual studio is waiting for internal operation to complete.' shows up.
I have reinstalled Visual Studio but without any luck. I've used ProcMon to check devenv and all the paths it shows, have to do with Android Studio.
I 'solved' the problem by accident. I disabled Source Control and for some reason, VS started working again. I know it's not an ideal solution but works just fine when you need VS urgently.
Don't know if Visual Studio is one of those programs. Someone correct me if I'm wrong, but I believe even after uninstalling, Visual Studio keeps some files in the registry from your previous installation and the AppData folder. You might want to clear those.
Close Visual Studio (if you haven’t already).
Open the registry editor (regedit.exe)
Delete the
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio{version}
Delete the
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio{version}_Config
Delete the %USERNAME%\AppData\Local\Microsoft\VisualStudio{version}
directory.
Use {version}=10.0 for Visual Studio 2010
Use {version}=11.0 for Visual Studio 2012
Use {version}=12.0 for Visual Studio 2013
Hope this helps
I have a newly built Windows 8 VM with VS 2012 Premium running on it, when I try open any sln file I get the following modal pop up error
Visual Studio 2010 Shell
Invalid license data. Reinstall is required.
I can open the sln's if I open up VS and then do project open, this is really annoying, any ideas how I fix it?
*Note I have done a VS repair and it didn't solve it...and I never had any VS RC release on the machine, all new build with s/w downloaded from the MSDN
Cheers
I encountered the same exact error when I created a solution with a full version of Visual Studio 2012 Professional on one machine and then tried to open the solution file with a copy of Visual Studio 2012 Express on a different machine. I got the error when double-clicking the solution file, but not when loading the solution into an already opened instance.
I fixed the error by opening the solution file (.sln) with notepad and changing the line that says Visual Studio 2012 to say Visual Studio Express 2012 for Windows Desktop.
After that, I was able to double-click to open the solution file on the machine that has Express installed.
I'm using VS 2013. I fixed this by right clicking the .sln and setting the Open With parameter to visual studio 2013 and not VS version selector or VS 2010.
I have faced the same problem. When I set the system Date and Time to the current Date and Time, The Problem solved by itself.
It looks like the .sln extension is owned by "Visual Studio 2010 Shell" a minimal version of Visual Studio that ships with products like SQL Server and Office to provide support for add-in development without any other features. Since this is a minimal version, it's unable to load any project type that ships with Visual Studio Express, Professional or above.
The same may happen when you have Visual Studio Express installed next to a full version of Visual Studio.
This may happen when you install an older version of Office or SQL Server after having installed Visual Studio. The old installer will hijack the extension.
To repair this problem:
use the "Open With" option of Windows and select the "Visual Studio Version Selector" as your default action.
Or open the "Default Programs" option in Windows, look up the .sln extension and make sure it uses the "Visual Studio Version Selector" as default:
Or locate Visual Studio 2012 in the Programs and Features window of Windows and chose "Change", the Visual Studio installer will pop up, chose "Repair" to have it repair the file associations and any other problems that may arise by installing Visual Studio versions in reverse order (it may for example mess up the MsBuild directory as well).
Remember that when Visual Studio 2010 was released, it could not yet know what Visual Studio 2012 would change, as such, it's best to install versions of Visual Studio in the order they were released. This may sometimes prove difficult, as other products may install Visual Studio versions without you knowing.
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...".