I have recently been having a problem with my Visual studios 2015 in which it stops working when i try to debug anything. I am able to build and rebuild the solution perfectly fine however when i try to debug it it simply stops working and a loads indefinitely. Also when i try to run the exe directly from the debug folder the windows explorer that i am opening it in does the same as Visual Studios. I have tried this with both complicated program and also just a super simple "Hello World" program. the language i am using is Visual C++. Any help would be appreciated because this is really annoying me.
After openning your VS 2015 and solution project, then if you experience the problem saying 'Visual Studio stopped working, close the program.....'
while you run or build the project that was previously fine; then run the command below in the command prompt
-> Go to command prompt
-> Go to C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE
-> Then run devenv/resetuserdata
-> Open the VS2015 and give your MS account for starting VS2015 as new instance
-> open your solution, build and debug, then ENJOY :)
Related
Visual studio crashes while building all.sln. I have all the source files. Chrome.exe is also working fine. But, It's been a week, I am not able to build chromium from Visual Studio. It shows this error message.
Unable to start program* allocator_clang_newlib_x64. The system can not find the file specified.
The all.sln is a very big solution with all the Chromium source code as Visual C++ projects. It will make Visual Studio slow even on high end machine. So the recommended way to debug your Chromium fork is via a standalone Visual Studio project. You can follow the steps below:
Open Visual Studio command prompt
Navigate to your Chromium's src folder from that CLI
Open Visual Studio to debug your Chromium executable by typing the following devenv /DEBUGEXE "out\YourBuildFolder\chrome.exe"
Press F5 to start debugging your source code.
Tip: If you want to start debugging by stopping at the entry point, on Solution Explorer pane, right click that project and choose Debug -> Step into new instance from the context menu.
You can use all.sln to edit the source code and yes you have to compile it again for the changes to take effect.
Since some days the feature files are broken.
VS2017:
Colors dissapeard, everything is white.
When I press F12 nothing happens.
When I run the test from solution explorer the tests work fine.
VS2015:
Everything works fine.
What I tried to do:
Option 1: Run Binding Tool
Right-click on the feature file
Select "Run Custom Tool"
This causes the SpecFlowSingleFileGenerator to regenerate the code-behind for your test framework.
Option 2: Restart Visual Studio
Close Visual Studio
Open Visual Studio
Reopen solution
This causes any bindings that haven't been cached to rerun.
Option 3: Clear SpecFlow Step Mapping Cache
Close Visual Studio
Open Windows Explorer
Type %TEMP% in Address Bar and hit Enter
Search for "specflow-stepmap-*.cache"
Delete those files
Open Visual Studio
Reopen solution
Option4: Uninstall and reinstall visual studio 2017
None of them fixes the issues for VS2017.
Some help is more than welcome.
I solved this issue by updating VS2017 to v15.6.1. Prior to that I've tried all the steps you mentioned and it did not work.
Also, found this article: https://github.com/techtalk/SpecFlow/issues/1049 which is saying the same.
These symptoms sound like you haven't installed Specflow extension on your VisualStudio 2017.
What happens when you dont have it is that VS can't work with feature files and can't navigate to anything when pressing F12.
Tests are working because VisualStudio executes already generated NUnit tests from feature.cs files.
Double check your VisualStudio Tools -> Extensions And Updates -> Check in Installed if you have Specflow for Visual Studio 2017 installed and Enabled.
Note: Each time you install a new Visual Studio you have to install the extension.
Came across the same issue, installed Specflow for Visual Studio 2017 from Tools >> Extensions And Updates and found as working fine.
Go the colours for feature file lines back and F12 is working fine.
Thanks.
I am using a Windows 10 64-bit laptop and when I try to debug any web project in Visual Studio 2017 (15.3.4) using IE11 as the browser, I get the error: "Unable to start program 'http://localhost/MyWebApp/'. There are no more files". The browser never even gets loaded, instead I get a popup with this error and nothing else. This error doesn't make any sense or give a clue to what may be wrong. Also, everything works fine with other browsers.
Please help.
In case it helps anyone. It now works again since I upgraded to Visual Studio 2017 15.5.2
Launch "Developer Command Prompt for VS2017" as Administrator.
From the command prompt run devenv.exe.
(Usually the path is "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\devenv.exe")
Works with Visual Studio 2017 15.9.20.
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 apologize as this may seem as bit of a general question.
I have developed a couple of VB programs using Visual Studio 2010 Professional and others on Visual Studio 2013 Ultimate. While I have not done any work in about a month with either version of Visual Studio, I thought I would go in and start work on a new project.
After entering some code in Visual Studio 2010 using WinForms, I found I was unable to run the code in the debugger (pressed the start button and F5).
It acted like it would start, then it just stopped and returned back to my code.
I thought I would try it on another program that was completed and working a couple of months ago, but I had the same issue present itself. Attempting to use Visual Studio 2013 had the same effect.
Any ideas from anyone? Has anyone else experienced this same issue recently? Once again, I do apologize for the lack of examples here, but I'm not sure what I can include to show the problem.
IMO, you should try resetting visual studio settings (and a restart may solve the issue)
you can try following
do it via visual studio -> tools -> import export settings
or you can run this command devenv /resetuserdata
or checkout this http://msdn.microsoft.com/en-us/library/ms241273.aspx