I'm trying to make use of Visual Studio's Emacs keybindings. In particular EmacsWordNext, I tried first mapping to Ctrl-Right, hit Assign and OK it didn't work, hitting Ctrl-Right doesn't do anything. I thought maybe because of the key conflict so I tried a different combo, one that didn't conflict, but same. I tried other Emacs binding but none did anything. I thought it was my Visual Studio on my machine, so I tried it on another machine but same thing...
Using Visual Studio 2015 Community Edition.
What am I missing? Any ideas?
HI this links below discuss similar issues you can try the solution there .
Using Emacs bindings in Visual Studio Community 2015
Related
Basically what the title says, I'm new to Unity and Visual Studio and I can't get Visual Code to autocomplete Unity's stuff.
I've tried almost every solution out there except for ones that were outdated.
I'm using:
Visual Studio Code 2022
Unity 2021.3.16f1
Tried almost all fixes on the internet but I couldn't get it to work.
A fresh Windows Installation did it for me!
Because of the M1 native support i started using Visual Studio 2022 Preview 5 (build 6509). The only problem i have is that i can't change my keyboard shortcuts. I can change the scheme but not any command separate. I have tried to use the Visual Studio Code scheme because on my instance of Visual Studio Code every shortcut is set correct (for me ;)).
Is there some sort of workaround to edit the keyboard shortcuts?
Cheers
I had the same issue, my workaround was to install the Visual Studio 2019 on my M1 MacBook and edit the shortcuts on the "old" version, seems like they share same .properties file.
I have installed Visual Studio 2015 Community Edition via Unity's installer and some of the options windows look like this:
Nothing fixes it; uninstalling-installing, formatting or installing on different machines. Apparently no one complains about this issue because there seems to be nothing on search results, but I'm 100% sure that everyone is experiencing this issue. When you open Visual Studio on its own, problem goes away, it works like it should. However, making Unity open Visual Studio causes it. I assume that this is caused by Unity forcing Visual Studio to load a plugin (probably Visual Studio Tools for Unity) which is actually incompatible with almost everything in Visual Studio.
Is there a solution to this problem? It drives me crazy and I don't want to use MonoDevelop.
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
In Visual Studio 2010 you can assign keyboard shortcuts for moving lines up and down.
I can't find these commands in 2012.
Have they been renamed or removed? Is there any way, out-of-the-box, to move lines using ALT + ↑↓? (I'm not buying ReSharper.)
This command is a part of Productivity Power Tools.
The 2012 version was released in November 2012. You can find it here:
Productivity Power Tools for Visual Studio 2012
Nothing happened to it, these commands don't exist in VS2010 either. Check what add-ins you've got installed.
Not sure what it does, but consider Edit.ScrollLineUp/Down. Default binding is Ctrl+Up/Down arrow.