Whenever I click "Attach to Process..." in the Visual Studio 2013 Visual studio crashes on me before seeing the attach dialog, regardless of if I have a project loaded or not. I can click debug and get into debug mode but I really need to attach.
Things I've Tried:
Uninstalled and Reinstalled VS
Loading Visual Studio with "/safemode"
Loading Visual Studio with "/log" and checking the log (no notable errors listed)
Deleting my Local Temp folder
Additional Info:
OS: Windows 8
Version: Visual Studio 2013 Update 4
Exeption when debugging VS crash:
An unhandled exception of type 'System.AccessViolationException' occurred in Microsoft.VisualStudio.CommonIDE.dll
Not sure what else to try or where else to look, I have VS 2015 preview install and it has no problems.
In my case the culprit was "PowerShell tools for Visual Studio 2013". I disabled it and the problem disappeared.
Tools => Extensions and Updates... => choose the extension and press Disable
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!).
Today my Visual Studio 2017 crashed during debug phase and after I restarted it, it showed this message:
"We've noticed that a tool window "Error List" is slowing Visual Studio"
What does it mean?
I think they resolved with Visual Studio 2017 update 15.6.0 as described here
https://developercommunity.visualstudio.com/content/problem/30884/error-list-slowing-visual-studio.html
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've installed visual studio 2013 and updated to 4 release, but when I connect to the internet and then try to open visual studio, the pop up menu open but visual studio does not run.
Have you installed "Microsoft Azure HDInsight Tools for Visual Studio"? If so, try uninstalling it.
The below thread saved me a lot of frustration (even though it says VS 2012, I had the same for VS2013 Update 4).
Visual Studio 2012 is unresponsive at start with hidden error messages (two dings at start)
You could also try running a repair on the install.
Or resetting the settings http://msdn.microsoft.com/en-us/library/ms241273.aspx
Or running in safe mode, maybe a plug-in is fouling it up http://msdn.microsoft.com/en-us/library/ms241278.aspx
Visual Studio 2013 Professional crashes when I try to open the Debug tab in the properties panel of a Windows Phone 8 project. No error given only "Microsoft Visual Studio 2013 has stopped working". Attached Visual Studio as a debugger and got the following error:
An unhandled exception of type 'System.NullReferenceException' occurred in Microsoft.VisualStudio.SmartDevice.ProjectSystem.Base.dll
I'm running Visual Studio as an Administrator
I have the same problem with a very weird behavior. The first time I create a WP8 project in VS2013 I have all the options for emulators, the designer, the devices and even the debug tab of the project working fine. All the markup of the mainpage.xaml is ok. If I close and reopen a new instance of the project in visual studio 2013, everything start having problems: I can not open the debug tab, the emulators optios are gone, the device windows appear in read only mode, The markup of the xaml says an "Invalid Markup" and got errors like:
The name "PhoneApplicationPage" does not exist in the namespace "clr-namespace:Microsoft.Phone.Controls;assembly=Microsoft.Phone".
BUT: It compiles and run in the emulator.
I also DO have all the Xamarin tools installed. It seems I am not getting this errors in Visual Studio 2012.
SOLUTION: From Xamarin Studio check for update and install the android SDK 4.10.2 and GTK# (2.12.0.0). At the time of this writing you have to subscribe to the BETA Channel to get this update. After installation you DONT have to delete de .suo file of the project and everything looks fine again in Visual Studio 2013