I am using Visual Studio with Unity. When I copy and paste a code in Visual Studio. It automatically adds an unnecessary namespace on the top. It is pretty annoying to see if there have many unused namespaces over time. May I ask if is this a bug or how can I turn off the auto import namespace when copy paste?
From the suggested name, I think Visual Studio confuses the "length" and "Length"
Here are the steps to reproduce the problem
On the top of the page in Visual Studio, go to Tools > Options > Text Editor > C# > Advanced > Uncheck the option for "Add missing using directives on paste" then click OK on the bottom of the page. And then restart Visual Studio.
Might be useful to some to note that tab completion will still auto-add missing using directives.
Here is an example with the option checked (the example specifics are not relevant but in this case an attribute is being pasted to an ASP.Net Core Razor Page):
Here is an example with the option unchecked:
Every time I type an emmet string and press tab visual studio replaces it with just the main element. Then i realized it was preferning the the snippet that it was auto suggesting. Is there a way around this or fix it? I am using Visual Studio 2013 Community edition on windows 7 64bit if that makes any difference
I found the problem, I was using another plugin called Viasafora that colors braces and makes it easier to to see your indentations it had a default option for showing completions ans you type. I had to go turn it off.
I cannot seem to find a solution: I am using Visual Studio 2013 Ultimate.
Can I change this GUID looking Default namespace?
Here:
There are couple of ways you can do it.
There is a property called ScriptProjectName that is only available through the Expression Editor. Setting it can change the project name and the namespace in the script. You need to set the expression and save the package prior to editing the script.
You can follow this article for more details.
I'm testing out Xamarin.Android in Visual Studio 2010 and have noticed that I have no Android Intellisense when I'm working in an Android Layout (.axml) file. However, I do get Android Intellisense when I'm working in a .cs file.
Example:
Here is a screenshot of my Main.axml file that lives in my Layout directory. Notice how the intellisense doesn't contain anything within the Android namespace.
What do I need to do to get intellisense to display the Android namespace in a .axml file?
Kannan Balasubramanian has posted an answer that worked for me (Binary Bits)
Here's Kannan's solution:
Most of the people who work with Xamarin’s Mono for Android in Visual Studio 2012 face a bug where Intellisense doesn’t work for AXML in source view.
One of the fix which worked for me is mentioned below.
Launch Visual Studio 2012
Open a solution with .AXML file in it
Now XML main menu should be visible on top
Open “Schemas…” menu
Sort by “File Name” column and see if “android-layout-xml” and schemas.android.com.apk.res.android” are there. If found, skip to step 13
If not found, go to “Program Files” if 32-bit system or “Program Files (x86)” if 64-bit system.
Then go to “\MSBuild\Novell” or “\MSBuild\Xamarin\Android”
You should be able to see 2 files “android-layout-xml.xsd” and “schemas.android.com.apk.res.android.xsd”
Copy these 2 files to “\Microsoft Visual Studio 11.0\Xml\Schemas”
Again open the “Schemas…” menu as mentioned in steps 3&4
Now click “Add…” button and add these 2 files which should be located as mentioned in step 7 & 8
Now restart visual studio and the XML editor for design layout should work fine with Intellisense
From step 5….
If above steps don’t work, then close the Visual Studio 2012.
Now open “Developer command prompt for VS2012″ under Windows programs menu.
Type “Devenv /ResetSettings” without quotes.
Launch Visual Studio 2012 and see if Intellisense works.
If still not working, better go to Xamarin forums and post there.
I just installed the latest release Xamarin.Android 6.0.1 – this may have been resolved in this release
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.