I have a new installation of VS2022 (Current). If I right click on some C# code it will show "Find All References (Shift-F12)". Clicking on it will work. However, if I actually press Shift-F12, it will open an embedded browser window pointing to www.bing.com. If I go to Tools/Options/Keyboard, select "Press Shortcut Keys" and press Shift-F12 it opens up the windows search screen rather than telling me what it's bound to within VS2022.
Any ideas how to diagnose or, preferable, stop this behaviour and revert to Shift-F12 doing "Find All References"?
So the answer to this one is on the weird side. Turns out I started using a bluetooth keyboard on the same day as starting to use Visual Studio 2022. The bluetooth keyboard treats the function keys as meta commands whilst the laptop keyboard does not. F12, of course, is "Open Search". To complicate matters, it turns out that Visual Studio 2022 intercepts this command. Whilst normally it opens up the Windows Search window, while in VS2022 in regular mode it instead starts an embedded web browser within Visual Studio. Not sure why you'd want that behaviour, but it does it.
The solution is to reconfigure your bluetooth keyboard.
Related
I would like to remove the Desktop tab from KDE Plasma desktop environment and get rid of the context menu. Is there a way to do this ?
Hi Chris, Thanks for the reply. I am running KDE 4.14.8. I am not seeing what you are describing. The context menu is the menu when you right click on the desktop. I think you are calling it "desktop menu". My original snapshot show that menu. That menu changed depending what desktop theme I selected. I could not find anything call Configure Desktop. The closest thing to that would be Default Desktop Setting and there is not there about the Tweaks tab. The project that I am working on is kind of mission critical. It would be just a plain desktop without anything. The only thing the user can do is log on, does his job and log off. All the things that can distract the user will be removed. I got most of them except for this pesky toolbox.
To remove the toolbox:
right-click on desktop to get the desktop menu
select Configure Desktop, a dialog appears
switch to Tweaks tab
uncheck Show the desktop toolbox
You can also drag it to a corner (when widgets are unlocked), then it will not show the current activity name, but will still be accessible.
The android studio shortcut for extract function is not working for me. If I press Ctrl+Alt+M nothing is happening and when I tried to remap it to the same shortcut, I noticed that android studio doesn't seem to recognize the shortcut at all. So I tested my keyboard and everything should be working. I even reinstalled AS no dice.
I found out that Nvidia Geforce Experience was capturing Ctrl + Alt + M shortcuts from android studio, even though I wasn't running any game, and didn't run any game recently.
To disable this annoyance go to Nvidia Geforce Experience settings and disable in-game overlay.
If it does't work check other program that you installed recently for some kind of overlay, hotkey or keyboard shortcut capturing.
I think some program captures this hotkey. See https://superuser.com/questions/1282799/what-is-preventing-ctrl-alt-m-from-reaching-intellij-on-windows-10, https://superuser.com/questions/11308/how-can-i-determine-which-process-owns-a-hotkey-in-windows. After an hour of finding hotleys with these programs I still don't know which one is capturing.
I tried some programs to show a list of Windows hotkeys. I tried to assign new hotkeys in AS and other applications (Libre Office). They don't catch Ctrl+Alt+M and Ctrl+Alt+Shift+M, while catch other.
Currently I use Ctrl+Alt+,, I added it to shortcuts (see below). You can also use Ctrl+Alt+Shift+T, then press 8. Or Ctrl+AltGr+M (right Alt).
UPDATE
On self-isolation I carried a PC home. Plugged another keyboard, now Ctrl+Alt+M works. Even if I assign this combination to other applications like Libre Office.
For Mac users: Command + Option + M
Shortcut Ctrl+Alt+M is assigned to other function in Android Studio, search it and change shoorcut. It will works
Besides what is already suggested as a culprit (Nvidia Geforce Experience in-game overlay), I found out another one.
When you have Macrium Reflect installed on your machine, the same shortcut will open a blank window (which is initially hidden in bakground, by the way, so the connection was not so evident).
I'm not sure what's the purpose of this windows, but right there you have the chance to enable/disable that shortcut, as in following picture:
I have a strange situation. IT installed SSMS on my laptop and it runs well the first time, connected to my SQL servers remotely etc. But then it's frozen. I forced quit and then started SSMS again. Now it's totally frozen, no popup window at all to enter the server-connection text string. Then I did a force quit and got a pop up window (see it here ).
Microsoft SQL Server Management Studio has detected that an operation is blocking user input. This can be caused by an active modal dialog or a task that needs to block user interaction. Would you like to shut down anyway?
Has anyone seen this before? My IT department has no clue.
Often this is due to the new connection dialog being off screen (usually due to changing monitor setup e.g. 1 to 2 monitors or resolution change etc).
If so the really easy fix (if your connection dialog just needed approval without changing fields) is :
Focus on SSMS and Hit Enter/Return
..or the easy fix (if above does not work - as your last connection is not ready to go) is:
Alt Tab to SSMS
Alt + Space - context menu
M - select Move (in offscreen context menu)
Arrow Key(s) - to move it back onto screen
As per answers here from #Eirik Toft and here from #Lee Chetwynd
Fixed an issue which presented the same on my machine today by renaming a entry in my registry:
After some digging there seems to be multiple issues that can produce the same error (Application, settings, registry). This blog entry covers it pretty well:
http://www.armedia.com/blog/2012/08/sql-server-management-studio-freeze/
In my case deleteing the SQL server management studio folder under AppData ( c:\users\%userName%Appdata\raoming\microsoft\ ) didn't work.
However I was successfully after deleting / renaming the regisitry entry:
[HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server]
(update)
Worked out the underlying issue on my laptop - was using additional 2 screens with much higher resolutions which caused windows / SSMS to open up the connect to new data source dialog off all of them. If your using multiple screens try returning to just use the native laptop screen to see if you can find the dialog that SSMS is waiting on your input for.
I just had this same situation, with two additional screens connected to my laptop. SQL Server Management Studio was opened on the third screen, with the modal dialog nowhere to be seen.
Two options:
Press tab three times and enter. This cancels the dialog. Now you can move the window to another screen.
Set Windows to only use one or two screens. SSMS opens on the first and should still open there when you move back to using three screens.
When SSMS is on your primary or secondary screen, the modal dialog opens on the first and should be usable.
It was because multi screen display. Turning off multiscreen to single one resolved it. Reenabled multi screen display after ssms started working
In my case, "Run as Administrator" option worked like charm. I was accessing my server screen with the windows RDP. And when I open SQL Server Management Studio and Visual Studio 2010 user hangs at the moment and wont operate unless sign off r disconnected by administrator.
But when I set compatibility mode of both the application to the "run as Administrator", it starts working fine.
the problem also occurs if you have a touch screen. I fixed this by disabling the local thouch screen when I switch to RDP.
When I run or debug a winrt application, Visual Studio 2012 seems to start it always on the same monitor.
How can I force Visual Studio 2012 to start the app on my other monitor?
Windows will deploy to which ever monitor you last viewed the Start screen on. So, here is what I do.
Start VS in Main Monitor
Bring up charms bar on Secondary monitor and select the Start charm
Launch debug from VS in Main Monitor
Your app should now launch in the secondary monitor.
I don't know if there is a way to set an option to do this - I haven't found one but haven't looked very hard since this works easy enough for me.
On Win8.1, it seems like the app always opens on the primary display. I swapped my primary and secondary displays (right click on desktop -> screen resolution -> "Make this my main display").
I also customized my taskbar so that it appears on all monitors (right click on task bar -> properties -> "Show taskbar on all displays").
I think, it is impossible.
The only solution you have is to move it to that monitor and then open Start Screen only on it while debugging.
In this case Win Store apps will open there
You cannot force the app to start on the second monitor but you can move Visual Studio 2012 to the second monitor and start the WinRT app on the first monitor. Swap or move the primary monitor if needed.
You do just active the Metro screen where you want to start the app ! Or after you can use these shortcut : Win+PageUp and Win+PageDown to switch
You can also drag the app itself to the alternative monitor. As others have noted, the apps will continue to open on the last monitor that you used.
Update: If you have Visual Studio 2013, the latest update remembers which monitor was being used to run the WinRT app and opens it on that screen.
I am having a weird issue with VS 2008 when I go to debug my program. When I click on the play button to run the program it flashes real quick and goes back to the VB IDE. No matter how many times I click on the play button it continually flashes and then goes back without displaying my form window or anything.
What type of setting would I need to change in order to correct this issue? I've been through most settings in the "my project" section and i do not see anything that could be causing it to do something like this.
My older vb apps I've made seem to work just fine when I click the play button on them. Only noticed this problem whenever I go and make a new vb app.
update video of what's going on
http://tinypic.com/r/2eycaas/7
Try this?
"
Did we install some third party Add-ins in your machine? If we disable Add-ins (“Tools” | “Add-in Manager”) and run “devenv.exe /safemode”, do we still have the problem? This can eliminate the possibility that third party Add-ins are causing problems.
We also can try to run devenv /resetsettings (Commonly, it makes sense than re-installation) or devenv /setup in Visual Studio Command Prompt.
"
--http://forums.asp.net/t/1324737.aspx/1
Just check your output window.
Accessible from Menu-> Debug-> Windows -> Output. (Check image:1)
In output window select Show output from: Build combobox. (Check image:2)
This will give you perfect idea what is happening.
Following are the guesses.
The VBC installer is not installed or corrupted.
Some addon is registered to run before compiling and is creating problem.
....Long list until you tell whats shown in output window.
Also check Show output from: Debug in output window and Final check would be Immediate window.
I feel this three would give you hint whats going wrong.
Fixed.
Changing it to x86 instead of Any CPU worked!!!! :) But question is, why me having an Core i7 Quad doesn't support the program when i choose x64.....
David
Is the startup form correct? You can see that in project properties.