How do I disable 'Just My Code' in Visual Basic 2005 Express?
It is supposed to be in menu Tools -> Options -> Debugging -> Enable Just My Code, but I can't find it.
This option is not available in Visual Studio itself for most Express editions (it is in Visual C# 2010 Express, though). For instance, in Visual Studio 2008 the options dialog is:
But in the Express edition, Visual Basic 2005 Express, "Debugging" is not available - only 4 of the 12 are:
However, the 'Just My Code' setting can be changed through the settings file, CurrentSettings.vssettings:
Open the settings file for Visual Basic Express 2005, CurrentSettings.vssettings (see below)
Change the value of JustMyCode from "1" to "0" - replace <PropertyValue name="JustMyCode">1</PropertyValue> with <PropertyValue name="JustMyCode">0</PropertyValue>.
Save the file, but under a different name, like JustMyCodeOff_CurrentSettings.vssettings.
Open Visual Basic 2005 Express.
Open menu Tools -> Import and Export Settings -> Import selected environment settings (the middle option) -> Next.
Choose “No, just import new settings, overwriting my current” -> Next (as we already have a backup copy in the old file that we didn't touch).
Press Browse to the new settings file, for example, JustMyCodeOff_CurrentSettings.vssettings.
Press Next and Finish.
Note that the line in the settings file containing "Just My Code" is extremely long, more than 200,000 characters, and not all text editors are able to handle it. The safe option may be to use a hex editor to change "1" to "0".
A common location of CurrentSettings.vssettings is:
C:\Documents and Settings\SomeUser\My Documents\Visual Studio 2005\Settings\VB Express\CurrentSettings.vssettings
Other settings for the debugger are:
ConfirmDeleteAllBreakpoints
StopAllProcesses
StopOnExceptionCrossingManagedBoundary
EnableAddressLevelDebugging
ShowDisassemblyWhenNoSource
EnableBreakpointConstraints
UseExceptionHelper
AutoUnwindOnException
JustMyCode
ShowNonPublicMembers
WarnIfNoUserCodeOnLaunch
AllowImplicitFuncEval
AllowToString
UseSourceServer
ShowSourceServerDiagnostics
AlwaysColorMarkerText
UseDocumentChecksum
OutputToImmediate
ShowRawStructures
DisableJITOptimization
ShowNoSymbolsDialog
HexDisplay
HexInput
AddUnmappedBreakpointAtMappedLocation
StepIntoOnRestart
ENCEnable
ENCApplyChangesOnContinue
ENCWelcome
ENCStaleCodeWarning
ENCPrecompile
ENCRelink
NOENCAllowEdits
NOENCIgnore
NOENCRebuild
ConfirmFoundFiles
DisasmLineNumbers
ModulesShowAll
UseCodeSense
DisasmFields
CallStackViewOptions
ShowExternalCode
SourceStepUnit
DisasmStepUnit
CrossThreadCallStack
SaveRemoteDumps
LongEvalTimeout
NormalEvalTimeout
QuickwatchTimeout
DataTipTimeout
AutosReturnValsTimeout
AutosRegistersTimeout
LocalsTimeout
RegistersTimeout
AddressExpressionTimeout
ScriptDocsTimeout
ImmediateWindowTimeout
SetValueTimeout
ShowNonprintableCharsAsGlyphs
ShowSystemProcesses
ShowProcessesFromAllSessions
EnhancedDataTips
UserSpecifiedEngines
OutputOnException
OutputOnModuleLoad
OutputOnModuleUnload
OutputOnModuleSymbolSearch
OutputOnProcessDestroy
OutputOnThreadDestroy
OutputOnOutputDebugString
OutputOnDebuggerMessage
VariableWindowIcons
DisableAttachSecurityWarning
LoadDllExports
NativeRPC
AllowSideEffectEval
EnableWatchTipBar
AutoLoadFromSymbolPath
LoadSymbolsWhenSettingsChanged
OneClickEdit
OfferArrayExpansion
VariableWindowPromptOnLargeExpansion
VariableWindowMaxSupportedChildren
PromptToAddSourceToIgnoreList
SourceServerExtractToDirectory
DefaultTracepointMessage
ProgramToDebugPath
AttachToProcessDefaultEngineList
SecureSourceLocalDirectory
SymbolPath
SymbolPathState
SymbolCacheDir
You can choose in option window "Show all settings". Then you will see also debugging options, I guess (I have VB 2010, and here it works this way).
Related
I've been using VSCode a lot lately and have gotten used to the keys-shortcuts/key-bindings (Ctrl+D, Ctrl+P, Alt+leftArrow, etc). However I've recently had some work where I needed to use regular Visual Studio (Microsoft Visual Studio Enterprise 2019) and it's painful remembering two different shortcut keys.
Is there a way to import VSCode key-shortcuts to into regular Visual Studio?
I've looked at this question and there wasn't much help besides manually changing them one at a time.
UPDATE: now the above post answers the question now that I posed Francois du Plessis's answer there.
If you go to Tools -> Options -> Environment -> Keyboard. There should be an option to select Visual Studio Code as a Keyboard mapping scheme
You can create your own settings file based on an existing Visual Studio file.
Simply add your settings to it from VSCode keybinding setting file.
VSCode's keybinding settings is stored in keybindings.json json-formated file.
open file in menu
File->Preferences->Keyboard Shortcuts
or on Windows file path like that
C:\Users\<user name>\AppData\Roaming\Code\..\keybindings.json
Visual Studio's keybinding settings is stored in CurrentSettings.vssettings xml-formated file.
on VS menu:
Tools->Import and Export Settings
then select 'Import select environment setting' radiobutton and click 'Next'
you'll see browser for import your file.
on Windows file path like that
C:\Users\<user name>\Documents\Visual Studio 2019\Settings\
You can read more about it at this:
Make Visual Studio use VS code shortcut keys/key bindings
In Visual Studio 2013, Microsoft again presents the menu in UPPERCASE as the default.
Can these be modified to be Sentence Case?
Yes - in the new Visual Studio 2013 (as in VS 2012), MS reinforced their design decision to make ALL CAPS MENU ITEMS the default. The methods for reverting the menu style are almost the same methods used for Visual Studio 2012, which has been discussed before.
Update (after Visual Studio 2013 Update 4)
As of Visual Studio 2013 Update 4 you can go into Tools > Options > Environment
and uncheck Turn off upper case in the menu bar
Before Visual Studio 2013 Update 4:
You need to create a specific registry key if you want "old-style" menus back.
First Variant: Since Package Manager Console is Powershell, select menu options TOOLS / Library Package Manager / Package Manager Console and enter and run
Set-ItemProperty -Path HKCU:\Software\Microsoft\VisualStudio\12.0\General -Name SuppressUppercaseConversion -Type DWord -Value 1
(as a single line).
Second Variant: Open up a Command Prompt (win+r, cmd, enter) and enter and run
REG ADD HKCU\Software\Microsoft\VisualStudio\12.0\General /v SuppressUppercaseConversion /t REG_DWORD /d 1
(as a single line).
Third Variant:
Change registry values by hand, open regedit and navigate to
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0\General
then, create (right click):
DWORD value
with the content of
SuppressUppercaseConversion
and set it to
1
Close regedit.exe and you're done.
Fourth Variant: At least one VS Extension (VSCommands for Visual Studio 2013) has been published that enables you (among other things) to switch menu style via config menu from within VS 2013.
You may also set it to all-lower-case items (which is, imho, nice):
switch to Sentence Case (subtly different from what you get with SuppressUppercaseConversion: the SQL menu gets renamed to Sql)
or hide it completely (and have it appear on ALT key press or mouse over)
After years Microsoft has changed their mind on this feature. As of Visual Studio 2013 Update 3 RC, an option has been added in Tools -> Options to change to Mixed Case for Menu titles. Obviously this is not for VS 2012 but going forward this option will be there.
Here is the notification from Brian Harry of Microsoft....
Mixed Case Menus – I know I’m going to get some feedback on this one :) This is a long standing request by a vocal portion of the VS user base since VS 2012 to change the “ALL CAPS” menus. In VS 2013 Update 3, we have added a Tools –> Options setting to control whether you see ALL CAPS or Mixed Case. The default is still ALL CAPS but, if you change it, it will persist across upgrades and will roam across your IDE instances using the VS Online roaming settings feature (if you log into VS so it knows who you are).
http://blogs.msdn.com/b/bharry/archive/2014/07/02/vs-tfs-2013-3-update-3-rc.aspx
I have been using the following reg files to enable/disable the lowercasing in Visual Studio 2013:
http://erwinmayer.com/dl/VS2013_ALLCAPS_Toggle.zip
Just double click on VS2013_ALLCAPS_Disable.reg inside the archive to disable all caps menu titles, and VS2013_ALLCAPS_Enable.reg to re-enable them.
You can easily edit the reg files before with a text editor to see what they contain.
If you're using the "Visual Studio Express 2013 for Windows Desktop" version the registry key should be added in:
HKEY_CURRENT_USER\Software\Microsoft\WDExpress\12.0\General
So simple! You can go to Tools -> Options -> Environment -> General tab and check the Turn off uppercase checkbox from the right side and click ok. Visual studio 2013 will automatically turn off uppercasing of the menubar.
VS 2013:
Tools→Extensions and Updates→Online,
Type "VSCommands" in search textbox,
Click Download
Tools→Options→VSCommands→General,
Click Open-Configuration button
IDEEnhancements→Main Menu→Change Main Menu Letter Case,
click Sentence-Case
My Visual Studio 2010 is too slow most of the time. So I decided to disable the vs2010 Intellisense. Can any one help me?
For C/C++: Tools -> Options -> Text Editor -> C/C++ -> Advanced -> Disable IntelliSense.
Update: This also works with VS2012.
Microsoft doesn’t provide any way to disable Intellisense. This wouldn’t be a problem, except Intellisense can and does crash.
To disable Intellisense, close Visual Studio and navigate to your vcpackages folder:
C:\Program Files\Microsoft Visual Studio 8\VC\vcpackages
Rename the file feacp.dll to something like foulup.dll. Now Visual Studio won’t be able to load Intellisense, but rather than crash it will just quietly drop its features.
or
Also have look to this solutions : how to disable intellisense...
Ctrl + J.
In case you are using ReSharper the way to disable IntelliSense is as following: ReSharper > Options... > Environment > IntelliSense > Autopopup > Enable Automatic IntelliSense Popup > Uncheck > Save > Profit.
This also works in Visual Studio 2012 for C#.
Simplest way I can think of: change the file extension association so that *.cs files open in a plaintext document window, not the C# editor. Repeat for other extensions as desired.
It's actually easy for most languages:
Select Tools/Options on the menu. On the Options dialog box, select Text Editor, then select the language you use, then select "General". Uncheck "Auto list members" and "Parameter completion".
Works on VS 2012, 2010, and others, and seems to be available for most languages including C#, Basic, and C/C++.
Change the file extension to ".txt "
Edit without intellisense.
Change file extension back to what it was.
When I double click an item in the find window, the C/CPP file opens in a tab next to the find window. I want it open in the main window (center) along with the other c/cpp files. Is there a setting to get this behaviour ? Thanks
Perhaps that setting has been modified somewhere. I've tried to reproduce the behaviour in a new(ish) installation of Visual Studio 2010, and can't reproduce. Perhaps you've chosen the C++ Development Settings where the behavior is different from the C# Dev Settings.
Consider resetting your Visual Studio 2010 settings.
Tools -> Import and Export Settings -> Reset All Settings
Introduction
I've always been searching for a way to make Visual Studio draw a line after a certain amount of characters.
Below is a guide to enable these so called guidelines for various versions of Visual Studio.
Visual Studio 2013 or later
Install Paul Harrington's Editor Guidelines extension.
Visual Studio 2010 and 2012
Install Paul Harrington's Editor Guidelines extension for VS 2010 or VS 2012.
Open the registry at:
VS 2010: HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\Text Editor
VS 2012: HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0\Text Editor
and add a new string called Guides with the value RGB(100,100,100), 80. The
first part specifies the color, while the other one (80) is the column the line will be displayed.
Or install the Guidelines UI extension (which is also a part of the Productivity Power Tools), which will add entries to the editor's context menu for adding/removing the entries without needing to edit the registry directly. The current disadvantage of this method is that you can't specify the column directly.
Visual Studio 2008 and Other Versions
If you are using Visual Studio 2008 open the registry at HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\Text Editor and add a new string called Guides with the value RGB(100,100,100), 80. The first part specifies the color, while the other one (80) is the column the line will be displayed. The vertical line will appear, when you restart Visual Studio.
This trick also works for various other version of Visual Studio, as long as you use the correct path:
2003: HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\7.1\Text Editor
2005: HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\Text Editor
2008: HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\Text Editor
2008 Express: HKEY_CURRENT_USER\Software\Microsoft\VCExpress\9.0\Text Editor
This also works in SQL Server 2005 and probably other versions.
For those running Visual Studio 2015 or later, the best solution is to install the Editor Guidelines by Paul Harrington rather than changing the registry yourself.
This is originally from Sara's blog.
It also works with almost any version of Visual Studio, you just need to change the "8.0" in the registry key to the appropriate version number for your version of Visual Studio.
The guide line shows up in the Output window too. (Visual Studio 2010 corrects this, and the line only shows up in the code editor window.)
You can also have the guide in multiple columns by listing more than one number after the color specifier:
RGB(230,230,230), 4, 80
Puts a white line at column 4 and column 80. This should be the value of a string value Guides in "Text Editor" key (see bellow).
Be sure to pick a line color that will be visible on your background. This color won't show up on the default background color in VS. This is the value for a light grey: RGB(221, 221, 221).
Here are the registry keys that I know of:
Visual Studio 2010: HKCU\Software\Microsoft\VisualStudio\10.0\Text Editor
Visual Studio 2008: HKCU\Software\Microsoft\VisualStudio\9.0\Text Editor
Visual Studio 2005: HKCU\Software\Microsoft\VisualStudio\8.0\Text Editor
Visual Studio 2003: HKCU\Software\Microsoft\VisualStudio\7.1\Text Editor
Productivity Power Tools includes guidelines and other useful extensions for older versions of Visual Studio.
Without the need to edit any registry keys, the Productivity Power Tools extension (available for all versions of visual studio) provides guideline functionality.
Once installed just right click while in the editor window and choose the add guide line option. Note that the guideline will always be placed on the column where your editing cursor is currently at, regardless of where you right click in the editor window.
To turn off go to options and find Productivity Power Tools and in that section turn off Column Guides. A reboot will be necessary.
Visual Studio 2017 / 2019
For anyone looking for an answer for a newer version of Visual Studio, install the Editor Guidelines plugin, then right-click in the editor and select this:
Visual Studio 2022
Same author as the package above but seems he had to split the extension to work with 2022.
https://marketplace.visualstudio.com/items?itemName=PaulHarrington.EditorGuidelinesPreview&ssr=false#overview
There is now an extension for Visual Studio 2012 and 2013:
http://visualstudiogallery.msdn.microsoft.com/da227a0b-0e31-4a11-8f6b-3a149cf2e459
If you are a user of the free Visual Studio Express edition the right key is in
HKEY_CURRENT_USER\Software\Microsoft\VCExpress\9.0\Text Editor
{note the VCExpress instead of VisualStudio) but it works! :)
This will also work in Visual Studio 2010 (Beta 2), as long as you install Paul Harrington's extension to enable the guidelines from the VSGallery or from the extension manager inside VS2010. Since this is version 10.0, you should use the following registry key:
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\Text Editor
Also, Paul wrote an extension that adds entries to the editor's context menu for adding/removing the entries without needing to edit the registry directly. You can find it here: http://visualstudiogallery.msdn.microsoft.com/en-us/7f2a6727-2993-4c1d-8f58-ae24df14ea91
This works for SQL Server Management Studio also.
I found this Visual Studio 2010 extension: Indent Guides
http://visualstudiogallery.msdn.microsoft.com/e792686d-542b-474a-8c55-630980e72c30
It works just fine.
With VS 2013 Express this key does not exist. What I see is HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0 and there is no mention of Text Editor under that.
For those who use Visual Assist, vertical guidelines can be enabled from Display section in Visual Assist's options:
The registry path for Visual Studio 2008 is the same, but with 9.0 as the version number:
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\Text Editor
For VS 2019 just use this powershell script:
Get-ChildItem "$($env:LOCALAPPDATA)\Microsoft\VisualStudio\16.0_*" |
Foreach-Object {
$dir = $_;
$regFile = "$($dir.FullName)\privateregistry.bin";
Write-Host "Loading $($dir.BaseName) from ``$regFile``"
& reg load "HKLM\_TMPVS_" "$regFile"
New-ItemProperty -Name "Guides" -Path "HKLM:\_TMPVS_\Software\Microsoft\VisualStudio\$($dir.BaseName)\Text Editor" -Value "RGB(255,0,0), 80" -force | Out-Null;
Sleep -Seconds 5; # might take some time befor the file can be unloaded
& reg unload "HKLM\_TMPVS_";
Write-Host "Unloaded $($dir.BaseName) from ``$regFile``"
}
You might be looking for rulers not guidelines.
Go to settings > editor > rulers > and give an array of character counts to provide lines at the specified values.