VS2015: Tooltips stopped showing when hovering on variables in Immediate Window - visual-studio

I remember some time ago I could assign a variable in Immediate Window during debug and when hovering mouse over I could see a tooltip with member values just like when hovering over variables in the code.
Now this feature stopped working in my Visual Studio 2015. Did Microsoft remove this feature in VS2015 or I messed something up? Is there a setting for this somewhere in the menus?
EDIT: Because not everyone is so sure about this feature ever existing, I add a screenshot from Visual Studio 2012 where you can clearly see the tooltips for text typed in Immediate Window (here I use the variable web):

Update:
I test it in different VS version(VS2012/VS2013/VS2015/VS2017), it really has this issue in VS2015 or VS2017. But it has this feature in VS2012 or VS2013.
I report this issue to the product team here:
https://developercommunity.visualstudio.com/content/problem/55570/vs2015vs2017-tooltips-stopped-showing-when-hoverin.html
If possible, you could also share your comment there.

Related

Mose clicks not registering in Visual Studio

This is not a coding question, this is a problem I frequently encounter in the Visual Studio IDE. My mouse clicks are often ignored if I work fast. Usually it happens when I click on a variable name, the studio starts loading a tooltip or a highlighter for that variable and I immediately click on another variable or any other place in the editor window - the click will be ignored. Has anyone experienced anything like this?
This started happening around 2 years ago, don't remember exactly when, but it was right after a new version of the Studio was released.

Visual Studio 2017 debug + double click on a component will not jump/create to the code

When I double click on a button in the designer while debug is running,
it doesn't bring me to to Button1_Click event (nor create it if not assigned).
Double click works in design mode of course,
but all previous VS: 2010, 2008, 2013 did have this behavior in debug mode.
(at least, in default setting)
Yes, it is not a good habit(?),but i really could use it.
Is it possible to enable this action in the debug mode in 2017?
Thanks in advance.
Picture:
In design-time, double click on the button will jump/create to the click() code.
But if i do the same thing # running debug mode, nothing will happen.
I think I could repro this issue in VS2010, but in VS2013 and VS2017, it really has no this feature. Maybe I use the latest vs2013 update version.
I help you report this issue to the product team here:
https://developercommunity.visualstudio.com/content/problem/147191/visual-studio-2017-debug-double-click-on-a-compone.html
You could add your comment and vote this issue in above developer community site.

Visual Studio 2012 Keyboard Freezing

I am having an issue within the razor view in Visual Studio 2012. For some reason, most of the time when I am trying to edit a style property, my keyboard freezes and doesn't allow me to type anything.
<section style="height: 15[Try to edit here]">
For instance, trying to add in a zero or 'px' where the "Try to edit here" has been placed above is impossible as the keyboard freezes.
I have ReSharper 7.1 installed, I'm not sure if that is the culprit?
Closing the tab and re-opening it fixes the issue, but it then re-occurs later on (not sure if there is a pattern as to when it re-occurs)
This happens to me often. I just switch tabs and come back and it doesn't happen(for sometime of course :-)). It could be some kind of unresolvable bug although i would suggest that you uninstall ReSharper and try again to see if it gets fixed.
It happens to me and my other colleagues as well.
I have found it to be linked to having a floating code window(s). Unlike the floating window for something like Find Results (without a title bar), these appear almost like another instance of Visual Studio. These do not come to the front when the main Visual Studio Window is selected. I have found the keyboard stops responding only on these windows if there is a Find Results kind of floating window open. When the problem occurs, clicking on another VS window and come back sorts it.
In earlier versions of VS, any pulled code windows appeared without a thick title bar and window controls box.
I tried posting images of the two kinds of floating windows but don't have enough reputation to do so! Let me know if it is confusing and I'll try to clarify.
This may not be the only way for this problem to occur but this is what I've observed consistently in the last few weeks of using Visual Studio 2012. I have C# environment settings with Resharper 7 and Reflector installed.

Prevent Visual Studio to scroll to the end of file when pressing Ctrl A (select all)

It's basically in the title.
Whenever you "select all" in the Visual Studio code editor, the editor will scroll down to the bottom of the file. Is there a way to prevent this?
I'm using Visual Studio 2008 at the moment, but this applies to all versions.
No, you cannot change this behavior.
Microsoft has been aware of this since at least VS 2010, but either doesn't think it's a bug or doesn't think it's important enough to fix.
From their response to a 2010 bug report filed on the issue:
We unfortunately do not plan to change Ctrl+A's scrolling at this
time, so we're unfortunately resolving this issue as Won't Fix for VS
2010. However, it will remain in our database to be revisited for a future release of Visual Studio.
Source: Microsoft Connect
A quick Ctrl-Z-Ctrl-Y will get you back to where you were. If you tend to do a Ctrl-S Ctrl-A Ctrl-C a lot then just get used to this whole chain instead: Ctrl-SACZY. Or, create a macro: https://msdn.microsoft.com/en-us/library/a0003t62%28v=vs.90%29.aspx
I was struggling with this myself, but the "undo" suggestion gave me an idea and I feel kinda dumb for not thinking of it earlier. Visual Studio includes "Navigate Backwards" and "Navigate Forwards" buttons (CTRL-, and CTRL+, respectively). So after you finish selecting and copying, simple click the navigate backwards button or type CTRL- and voilĂ ! you're back where you were.
I know it doesn't stop the scroll to begin with, but at least it puts your cursor back exactly where you left it!

Visual Studio 2010 events button has disappeared

Hi I have been working with visual studio 2010 ultimate all day developing an asp.net webforms application.
I just realized that on the properties for controls window the button for events is missing , the one that looks like a thunderbolt.
An hour ago that button was there and now somehow it has disapeared and I can't figure out how to make it visible again.
I have tryed reseting the visual studio settings and reseting the computer but nothing worked
How can I get the button back?
I had the same problem. This helped me.
1.Restart visual studio 2010.
2.Click and select a control in markup page(.aspx)(like
3.After selecting , Click "View" in menu and select "Property window".
Check the property box, Thunderbolt ll be available. It just happened for me!
If the above solution not working go on with this!
1.Select design view in markup(.aspx)
2.Select any individual control like a button or label..
3.Now, you will be able to see a ">" button on the right side? Click it.
4.Remember to select only one control./.now check your property window! Whoohoo..
Actually while the solution above works, it puts you through more steps than you need. You can resolve this famous disappearing thunderbolt by simply clicking on Design view, and then clicking back on Source view, then clicking again to select the control in source view.
The Thunderbolt icon and events for the control will magically reappear.
You do not need to restart Visual Studio, and you do not need to select anything while in Design view.
And now, for my RANT about this annoying bug:
Even though this is easy to resolve, it is a MAJOR inconvenience to developers in my opinion, because we have to do this silly workaround all the freaking time.
This is in fact a BUG in Visual Studio. It has existed since at least Visual Studio 2010 (many users have reported it here and in MS forums across this and all later versions of VS). I have confirmed that this bug still exists in the latest build of Visual Studio 2022. So clearly MS has no plans to fix it.
[Rant Mode Off]
Cheers,-=Cameron

Resources