Why aren't my Microsoft Visual Studio 2017 debugging toolbar commands showing? - c++

I can't see neither my breakpoints or any debugging commands. I have installed Microsoft Visual Studio 2017 and I'm currently editing a c++ source file and i'm having big troubles with debugging. Does anyone know a fix?

Reinstall VS should be the last resort, you can try below suggestions first.
Please try to restart VS 2017 and if it doesn’t work, try to reboot your machine.
Please try to repair Visual Studio like Alan mentioned, in Visual Studio Installer > find Visual Studio 2017 > More > Repair.
Make sure that you are not using some extensions which may cause incompatibility. If you installed some extensions, please try to disable them temporary(Tools > Extensions and Updates… > find the extension you installed manually before > select it > Disable) and restart VS 2017.
Also, please try to delete the hidden .vs folder in your solution folder, and then try to start debugging again.
Sometimes, updating VS 2017(VS Installer > find VS 2017 > Update) will work.

Related

Can't install extension + version selector shows empty list

Edit: After wait too long, I have resorted to do a clean install of Windows 7.
It solves everything.
I believe the cause is : some Windows files, or some service are disabled, by me or virus.
Now, I can no longer test any solution so I accept the existing useful one.
Original Question
My Visual Studio 2017 can run & compile C++ code, but :-
(main problem) can't install any Extension (double click .vsix yield nothing)
double click .sln will popup "Choose Application" that shows no choice. (but "Open with..." works OK)
This issue happens only to my computer in workplace.
It had worked OK before I cleaned up my system.
I tried :-
install, uninstall and repair Visual Studio 2017 several times.
https://github.com/Microsoft/VisualStudioUninstaller
%ProgramFiles(x86)%\Microsoft Visual Studio\Installer\resources\app\layout\InstallCleanup.exe -full then reinstall (can remove "(2)", but not other symptom)
update to the latest version 15.9.17
(Thank comment from Jeaninez - MSFT) Make sure my .sln start with this at the first line:-
Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio 15
I believe the issue is related to Microsoft Visual Studio Version Selector.
This symptom might come after I uninstall VS2019.
My system might be broken?
Perhaps, the cause may be somethings very deep in OS. I am considering reinstall Windows 7.
Reference:
Why I think it is Version-Selector-related : Can't install the extension on Visual Studio 2017 after installing Visual Studio 2019
Similar question (2014) : How do I add versions to “Visual Studio Version Selector”, my list is empty (repair not help)
Visual Studio Version Selector Doesn't open (2010)
Best link about (2) : https://developercommunity.visualstudio.com/content/problem/251934/vs2017-community-edition-shows-2-in-title-name.html
To install extensions, try to find VSIXInstaller.exe on your disk. Normally it is installed here:
c:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VSIXInstaller.exe

The setup for this installation of visual studio is not complete, really?

I have been using Vs 2017 for several months on dev machine. This fine morning says setup incomplete. Am I missing something?
In this case you need to go to Control Panel => Programs and Features and choose Visual Studio and update it.
VS 2017 (15.6.6) was fine for me on Friday 6/1/18 on Windows 10, but same issue as OP today after a restart.
As suggested by the dialog and Retired Ninja, I ran the Visual Studio Installer (to 15.7.3 after updating VS Installer) and that fixed it.
Note that the 15.7.3 update was a 7.73 GB download. Your download size may vary.
This has happened to me for the last 3 upgrades in Visual Studio Enterprise 2017 (now again on upgrade to 15.9.21).
The fastest fix (and I'm not sure why) is simple and doesn't bomb your settings or take for ever.
In the Visual Studio Installer, click on Modify.
Click "Modify" on the bottom right corner.
Yes it says "Total space required 0 KB".
Yes you didn't really change anything.
It will then act like it is downloading something. (not sure what)
It will then act like it is installing something. (again, not sure what)
Open Visual Studio 2017 and it works.
Hope this helps.
If you have an offline installation like me and can't simply re-run the Visual Studio Installer you can edit devenv.isolation.ini and change the last line to read SetupFinished=true. It will detect your trickery and complain, but at least it will launch again.
Edit: I ended up getting the Visual Studio Installer to fix the issue after choosing the "Download then Install" option. Maybe I was too impatient when I initially stopped the update? My above answer is useful when you need to get work done that isn't affected by the broken features, but you will likely encounter problems later on.
just had the same problem (without any reason with) vs 2019 prof, after googling and reading on that topic, just went to vsix, looked for some individual component to install/uninstall, randomly picked cloud explorer, uninstalled it and some dependent components and VS 2019 prof started normally
decided to leave this here. may be it helps somebody
Solved: I did following steps, run the visual studio and it works for me.
In my case visual studio was working fine , I just restarted the PC, this popup was keep coming when I try to open visual studio.(in my case I was using VS 2019)
Go to this path "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE"
Open devenv.isolation.ini, set SetupFinished=true and save.
Now open visual studio.
Cheers!
In my case did following steps:
Clear temp files (you can %temp% in run command and Shift+Delete files)
Restart your computer
Open visual studio it will work properly.
Update: Faced problem again after couple of days, This time I go to C:\Program Files (x86)\Microsoft Visual Studio\Installer.
Click on retry.
Select one more feature which I had already installed on my Visual Studio
Click on modified and after installation it worked again.
This happened to me after I canceled a plugin update.
I solved by going to this site that has the latest update of Visual Studio.
https://learn.microsoft.com/en-us/visualstudio/releasenotes/vs2017-relnotes
I downloaded and upgraded it.
After that, Visual Studio worked.
If your VS is already upgraded, there´s an option to "repair" on the installer.
For this problem, goto uninstall screen in control panel right-click visual studio and select option change, Installer page will open now, In that window without changing anything click modify. it will solve the problem. I'm using VS Professional 2017
I got the same error today morning. This is what I did:
I ran the visual studio installer then I clicked on Modify.
The installer was showing 0KB Required. I continued and then it downloaded and installed. (Not sure what).
After that installation, it was able to launch.
I hope it works for you as well.
I was using Vs 2019 professional 16.6 and happened to me this issue one morning. I modified the installation by adding Azure Development tools even though I was not using it. This fixed the issue.
I just updated to 15.9.24 and I got this yet again, as I have my resolution above, and Visual Studio 2019 seems to be a lot better with avoid this issue. The installer for 2019 you do have to change something and do the modification, 2017 you don't have to change anything.
I reported this issue through Developer Community:
Setup not complete since 15.9.21
I don't know why but sometimes its buggy
it's up to date but after launch visual studio this error prompted !
you have to click modify in vs installer and just modify it.
its not going to download anything.
after a moment launch vs and enjoy :)
For VS2022, WIN11:
Control Panel > Programs > Programs and Features > Microsoft Visual Studio Installer
Then, click on Change and resume the previous process.

Using UE4 with Visual Studio 2017

I recently did some cleaning of my drives. I decided to install visual studio 2017 after cleaning the drives up. I have been trying to continue work on my old UE4 project using the engine pulled from GitHub. I tried rebuilding the project with VS2017 which I know is not fully supported yet. I did run into quite a few problems, including the missing corecrt.h files. I reinstalled the Windows SDK to fix this.
The current problem is a new missing file called windows.h, and I believe it is missing due to the build tools looking for the wrong version of the SDK. I was wondering, has anyone else successfully integrated Visual Studio 2017 with their UE4 project after running into similar problems?
-- Edited due to poor grammar.
As I know Version 4.15 supports both Visual Studio 2015 (default) and Visual Studio 2017. If you are building the Engine from source code, you would want to open a command prompt after running Setup.bat and run the command GenerateProjectFiles.bat -2017. This will give you a Visual Studio 2017 solution for the Engine.
To use Visual Studio 2017 for projects, you can set your preference for which version projects use by going to Edit -> Editor Preferences -> General -> Source Code and choosing Visual Studio 2017 in the Source Code Editor setting.
If regenerating the Engine's VS project files doesn't help. Try regenerating your own UE4 project's VS project files.
With Visual Studio and UE4 closed, find the .uproject file, right click and select Generate Visual Studio project files.
Open the solution, make sure your UE4 game (e.g. MyProject) under the Games folder is set as the StartUp project (right click, Set as StartUp project), then try a compile.

Visual Studio 2015: Build successful but debugging never stops loading

I have this C++ project I am trying to debug in Visual Studio (Community) 2015. The build is always successful, but after that debugging never starts. All that shows up is the Windows loading icon, which just never goes away. Any ideas about what might be wrong?
The problem was that Avast was interfering with my Visual Studio Projects. I used the instructions at https://forum.avast.com/index.php?topic=139935.0 to get it to work.
Basically you need to exclude your VS projects from Avast's scan.
... but simply turning off DeepScreen in Avast 2014 is not enough. I
make multiple apps in Visual STudio 2012, and I can tell you that even
with Deep Screen off, Avast will still pop right up and destroy the
compiling process by saying the .exe is a virus (the crazy "evo-gen
[susp]"). The only way I can get Avast to stop doing that is to
manually enter-in exclusion directories for every directory where I
create apps! ...or make an exclusion for some high-level folder.
Try resetting your settings by going here
Tools >> Import and Export Settings Wizard >> Reset all settings
I had similar problems for Visual Studio 2015 Update 1 on Windows 10.
For me, the only solution, which helped is to install this package:
https://www.microsoft.com/en-us/download/confirmation.aspx?id=49029
"FIX: Devenv.com process freezes after you execute devenv.com /build command in Visual Studio 2015 " https://support.microsoft.com/en-us/kb/3092422

cannot create c++ project in Visual Studio 2010

I suppose since I installed Visual Studio 2012, I cannot create C++ project in Visual Studio 2010. But, I am not sure new installation of VS 2012 is related to this problem.
The problem I am really struggling is that neither hint message nor notification are shown when I try to create a new C++ project.
I have tried several ways from google even include stackoverflow, but failed.
Is there anyone who knows any solutions or has any workarounds?
1) I wouldn't be at all surprised if installing MSVS 2012 is the culprit. VMs are Good :)
2) You should definitely look at the Windows event log (if you haven't already)
3) You can also run MSVS 2010 with logging as follows:
http://msdn.microsoft.com/en-us/library/ms241272%28VS.80%29.aspx
Devenv.exe /log "C:\My Files\MyLog.txt"
i faced the same problem in "microsoft visual studio express 2012 for window desktop" and now it's perfectly working after having gone through repair option.
If you have another version (or express edition) of visual studio installed on the same PC that is previously used to create console applications, that might be the issue. I had the same issue and I had Visual C++ 2008 on the same computer and I could either use the visual C++ for console applications or uninstall it completely. Hope this helps!