I have an xml comment on a function that throws a std::runtime_error. While the intellisense shows the exception type that is thrown, it isn't showing the description.
I searched about it but nobody seems to have a similar problem. I also tried restarting Visual Studio but still nothing.
Related
I have a problem in Visual Studio 2022, when I have syntax error and I hover over the underlined part in code, nothing happens.
E.g. I do not put ";" at end of line, it shows it as error in error list window, but hovering over it does nothing.
There should be some suggestions for fixes or more info about the error but there's nothing. The error list window does display the error message and all about it as excepted. I have tried repairing the VS, uninstalling and installing few times including deleting any leftover files I could have tracked on my system, but nothing helped. I reset all settings in VS too.
Any suggestions as to what to do?
Is there maybe some shortcut that enables/disables it that I could have accidentally hit?
I am having a very strange situation over here.
I refered to the UWP samples and tried Custom Media transport controls sample. I ran it and it was working just fine, like its supposed to work. But then I tried and made my own project and I copied exactly everything which was in sample project not even name of file or folder was different. And then when I ran that project it gave me debugger unhandled exception and open App.ig.cs some file like this and when i continue it stop debugging. Below is the attached snapshot of that error. Any help is appreciated this is a really strange error for me as it makes no sense at all.
Note: I have tried to run it in both blend and visual studio
I solved it by simply ignoring the style of transport controls provided in the sample, for some reason that style was not able to verify some properties so I deleted that file and made my own style file, I copied the style of default media controls and edited them, it worked for me :)
I just found the very handy "TRYCF" hotkey in VS2015 - for those unaware, you can type "trycf", hit tab and it lays the following out for you:
Try
Catch ex As ArgumentException
Finally
End Try
This would be amazing, and would save me a lot of time in my day to day coding, except the default exception type "ArgumentException" is no good for me, I just want to catch generic exceptions: "ex as exception"
Does anyone know how I can set VS2015 up so that the default exception is just an "exception"?
Cheers.
You are invoking a code snippet. You could edit the snippet file and change the <Default> tag.
For VS2015, the path to those snippets is: "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VB\Snippets\1033\common code patterns\exception handling".
A recommended alternative is to copy the subject snippet to your personal snippet folder.
C:\Users\UserName\Documents\Visual Studio 2015\Code Snippets\Visual Basic\My Code Snippets
Then edit it to change the <Default> tag. Also change the <ShortCut> tag so that it does not conflict with the pre-installed VS snippet.
Our team is porting an existing Universal windows application (8.1) to Windows 10. After installation of VS 2015 we faced with lots of weird problems in xaml editor. For example:
Ivalid type: expected type is 'DataTemplate', actual type is 'DataTemlate'.
or 'Ivalid style target type: expected type is 'ProgressRing', actual type is 'ProgressRing'.
Similar errors are everywhere in XAML files. Please, see some screenshots attached.
Has anyone faced with similar issues? At runtime everything works fine, by the way.
It may be related to Resharper. I do have the same problem but only if Resharper is enabled.
If you are using Resharper, try suspending it, then re-open the designer and see if you still have the problem.
"'DataTemplate', actual type is 'DataTemlate'"
Seems like a spelling error, although it's odd that this still compiles fine, because it should not be able to find this type if it is spelled incorrectly.
I seem to be having an issue using the call stack viewing functionality of Microsoft Visual Studio 2010 Professional.
During debugging, my application crashed, so I inspected it with the call stack view.
The offending line was contained within called showInDGV(...) nothing exciting, just trying to read an uninitialized variable or something...
All well and good, so next thing I did was check to see where the call to showInDGV() was coming from, because it is called from multiple places.
When double clicking the entry in the call stack (the entry that should highlight a showInDGV(...) subroutine call), the IDE highlighted the incorrect line.
Instead of highlighting showInDGV(), it highlighted the next non-empty line below it, which was End Sub
Clearly something is wrong here....
So I inspected the call stack further - turns out Visual Studio is highlithing the wrong line whenever I try to debug using the call stack.
This isn't actually the first time this has happened. In fact, it seems to always happen when working on a large project.
Initially, the call stack works properly and highlights the correct line, but at some point it gets messed up, and then it never seems to fix itself, even after closing and re-opening the program.
Does anyone know the cause/solution to this issue? I figure it might be some sort of corruption in the visual studio project, and I considered copying and pasting the source code into a new project but even if that fixed it, it wouldn't prevent it from happening again.