I think I accidentally changed some settings in my MSVC 2010 compiler and now I can't find the compile and execute option. Also when I hit the tab button for indentation an arrow(->) appears. I wonder whats wrong??
Use the tools menu "Import and Export Settings" then select "Reset all Settings" to reset the settings back to default.
To reset editor blunder, just hit Ctrl+Shift+8, from inside the text editor itself. This is toggle-able option, which can be used to see white spaces. Sometimes useful!
Related
I often use VS 2019 (16.8.5) to profile applications developed with Qt on Windows (10). I've got it configured as an external tool in Qt Creator.
However, every time I open it by just running devenv.exe, I have to go through the same process of clicking "Continue with No Code" on the startup welcome screen, then selecting Debug → Performance Profiler from the menu. I'd like to automate that as much as possible.
So my question is: Is there any way, from the command line, to start the IDE, skip that welcome screen, and go straight to the profiler? If not, can I at least skip the welcome screen?
I looked in the manual but couldn't find anything that seemed to do the job (/NoSplash doesn't skip the welcome screen, btw). However, I noticed that the output of devenv.exe /? in the console listed a slightly different option set, and also there's the /Command switch (which I also read the docs for), and both of these together, combined with past experience, lower my confidence in the completeness of the documentation there. I also found Running the Visual Studio Profiler from the command line but it discusses using the command-line profiler directly; I want to run the graphical profiler in the IDE, though.
If there's no way via devenv.exe, is there maybe some other way to automate this? And if there is a way, the bonus question is: Can I go further than just opening the profiler and actually start profiling given an executable filename or a running PID?
You can start VS and open the profiler like this:
"C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\devenv.exe" /Command Debug.DiagnosticsHub.Launch
It is easy to configure Visual Studio Code to your liking through its various settings. Nearly every part of VS Code's editor, user interface, and functional behavior has options you can modify.
in order to stop the welcome screen do the following things
go to File > Preferences > Settings
search "Startup Editor"
choose "None" from the drop-down menu
in order to edit / make a new screen when app started follow the below steps
go to File > Preferences > Settings
search "Startup Editor"
choose "NewUntitleFile" from the drop-down menu
Setup your own file
After upgrading from Eclipse Neon to Oxygen I noticed that I can no longer navigate around the code by clicking on definitions while holding the Ctrl key down. The indexer itself works fine, and I can still jump around by pressing F3 or using the context menu.
I am using Eclipse CDT with C++.
The following screenshot proves that the feature is enabled:
What am I missing?
You're probably running into bug 517610. Note the following workaround from the bug:
To work around the problem, you can disable the Change Log hyperlink
by going to Window > Preferences > General > Editors > Text Editors >
Hyperlinking, then untick "Changelog Detector".
The bug fix is scheduled for Oxygen.1, which will be released on September 27th 2017. Alternatively, you can update to the latest development build (6.1.0) of Linux Tools (which is the component that contained the bug) via the update site http://download.eclipse.org/linuxtools/update/.
In addition to the first solution, increase the "Maximum number of tokens per translation unit" in your Eclipse.
I can not type in the terminal:
What is the problem? Help please.
I have Windows 10. I went to CMD properties and enabled the "use inherited console" option. (Sorry, my print is in Portuguese. But I think it will help.
I had the same problem. Disabling "experimental features" for cmd did the trick for me. Right click the title bar of the cmd and go properties.
Be sure to restart Webstorm or PhpStorm after doing these.
For Windows 10:
Just check the "Use legacy console" option.
For Windows 10 Technical Preview: Uncheck "Enable Experimental Console features" in "Experimental" tab
Try adding new terminal tab (open new session) by pressing the green PLUS sign (or right click->new session).
This worked for me.
I set debugger to Native Only, solution configurations is Debug but New Data Breakpoint... option is still greyed out and I can't use it. Can anyone prompt me what else I need to change ?
Make sure active project debugger setting is "Native Only".
Start the debugging with another ordinary breakpoint, then you can see "New Data Breakpoint" is clickable. (In other words, you must be inside debug mode to be able to create a data break point.)
Hope this helps..
Also be sure to look at Tools -> Options -> Debugging -> General and make sure "Enable address-level debugging" is checked.
I'm trying to learn to love Visual C++ 2010 Express, but it is difficult! I've just created a "Hello world" console app and compiled it - no problems. I now want to run it. It seems the only option open to me is to run it in the debugger - there is a "Run" button on the toolbar but it is disabled. I don't want to debug it - I really don't like debuggers! Is there any way of just running the app from inside the VS IDE?
If you can't see the "Start Without Debugging" command in the toolbar, go to "Tools -> Settings -> Expert Settings". Basic Settings hides lots of stuff you probably want to see.
Professional version of VC2010 doesn't seem to have this switch.
Open the Tools menu
Go to Customize
Switch to the Commands tab
Select the Debug category
Drag the "Start Without Debugging" command to the Debug menu item
Edit: Full disclosure, I don't actually have VC++2010 Express installed on this computer, so I'm just sort of winging it here.
If you want to have a "Start Without Debugging" icon on the menu bar instead of in the drop-down Debug menu (even if Tools->Settings = "Basic Settings"), do this:
Tools->Customize->Commands->(choose Menu bar)->Add Command->Debug->Start Without Debugging->ok.
Then Move Up/Down if you want to change its position.