I'm debugging my code in visual studio 10, I press f11 step into my own function (which by the way is in the SAME source cpp file as the current function) and I always get "No source available"!!
Then I tried putting a breakpoint in said function and when I run visual studio it breakpoints and says: "No source available"
I can step over the function but I can't step into it
Another problem that may or may not be related is that every 5 minutes, Visual Studio 10 will suddenly for no reason stop recognizing all of my variables and functions, giving all of them a red underline. It will still compile fine. But the red underlines will say unrecognized variable etc. Then I just right click on one of them, click "go to definition", it brings me to the definition and when I go back to the original window all the red lines have magically disappeared! This does not seem right; forcing visual studio 10 to just take me to the definitions will suddenly make it realize that they exist? Then 5 minutes later the red underlines appear again!
In VS 2010, click on "Project, Rescan Solution". The red underscores go away (for now, at least :o).
The red underscores started appearing a few days ago, two years after I began using VS2010.
With respect to your "No source available", did you by any chance disable debugging info for that particular module? (See "Properties").
Related
Sometimes in VS2017 Visual Studio takes forever to run a new project and all the while it is showing an icon in the bottom of the status bar that looks like this:
I would guess that this means that it's downloading something, but what? It's frustrating that Visual Studio doesn't provide better messaging about what's going on given that sometime the process may take five minutes or more and I'm not sure what it is doing.
What does this icon mean? And is there any way to see what Visual Studio is doing in such a situation?
I found a related question Visual Studio stuck initializing with strange icon in status bar but it does not answer my question.
It isn't about downloading. Visual Studio 2017 (and earlier versions as well) shows this icon in the status bar during the building process.
You can see more information in the Output window, click View → Output
You may notice that suddenly a project that normally builds quickly is taking a long time to build.
I've now personally been caught by this about 3 times myself.
This can occur in VS 2017 because VS 2017 has code analysis available. If you compile your project using "Debug with code analysis instead of "Debug" selected this will run full code analysis on your code during the build process.
I just opened a project that i havent opened for awhile and "debug with code analysis" was the default option when i opened it. So this caught me just a few minutes ago.
What makes this confusing is that the drop down box in visual studio is not very wide. So it is often difficult to see that you are compiling with code analysis because the text is cut off as can be seen in this image below and a developer only sees "Debug w" and they don't realize they are compiling with code analysis.
Hope that helps.
thanks
Matt
I was coding a windows 10 uwp app. All of a sudden all my files starting getting green squiggly lines under them. I've tried cleaning, rebuilding, exiting visual studio, restarting computer, and even creating a new blank windows 10 uwp app using Template 10. None of this has solved my problems. I can't remember exactly what I did to cause this problem in the first place. I remember selecting one of the "Show potential fix". In the first image all the using are marked in green. And in the second image the project compiles fine but it is giving red marks all over.
How do I get rid of the green squiggly lines?
Update: added another image with red lines.
I haven't used my VS in few months, but today I got the need to. So I wrote some code, pressed F5 to see if it compiles and works properly, it started showing compiling process in the bottom window, at the very bottom a Build Successful message shows up, and nothing. The app doesn't start up, I can't click anything in VS (isn't considered as "not responding" by windows), and Task Manager shows three processes named like my app, all having 112K memory usage. After I kill VS process, one of them closes, but I absolutely can't get rid of remaining two, until I restart my PC. Trying to run the exe in project directory also didn't work.
I'm reinstalling Visual Studio to see if it gets fixed from just doing that, but ideas on how to fix it are still welcome in case it doesn't.
I'm having an issue with CodeLens in Visual Studio 2013. I recently upgraded Visual Studio 2013 Profession to Ultimate. I have CodeLens turned on:
But for some reason, Visual Studio is just inserting a blank line where the "references" should go:
You can see the blank line between lines 79 and 80. It does this with every project and every class in any project I open.
Does anyone know what could cause this?
These are not simply "blank lines", at least they shouldn't be.
This is the space that CodeLens reserves for its information. As you see here, there is small text above the declaration for information like "2 references".
If you open a project, it will reserve this space (because it knows it will need it later) before it can actually display this information (because the full project scan takes time, more time the larger the project is)
Now, load a small project and wait a little for the info to appear. (Have an eye on the task manager while doing nothing.) If it does not appear, something might be wrong with the IDE. Maybe the text color is white on white? Try resetting the settings.
The issue seemed to fix itself when I upgraded to Visual Studio 2013 Update 5, released on 7/20/2015. My CodeLens now works as expected and shows information rather than a blank line.
I was using TypeScript 0.9.5 during a project, and then upgraded to rc1.
After I did this, although TypeScript is installed and my code works as expected, I have lost all formatting and intellisense.
I have uninstalled Visual Studio and done several reboots. However, I still come back to the same issue.
Has anyone experienced this and know a way to resolve it?
Further Findings:
It is impossibly slow to type source code. Often resulting in the blue warning "Formatting Task Took Longer than 2 seconds to complete. Please try again..."
'It is impossibly slow to type source code. Often resulting in the blue warning "Formatting Task Took Longer than 2 seconds to complete. Please try again..."'
I had the same w/ clean install of VS2013 Express Web Update 2 RC and found this old bug which was fixed a year ago so it seems to be a regression. Here's the workaround from the post:
This is caused by an infinite loop in the logic that detects the extent of the statement that needs formatting after semicolon...go to your Tools\Options dialog then to Text Editor\Typescript\Formatting and check off "Format completed statements on ;". this will disable formatting after semicolon obviously, but should make VS usable again; this should not affect other formatting trigger points like new line and closing parentheses.
Restart Visual Studio for the change to take effect.
FYI: I've submitted a bug report to Microsoft on this issue. Perhaps you could vote it up the bug ticket.
The following worked for me => click on
Tools
Options
Text Editor
All Languages
Ensure "Auto list members" and "Parameter information" are checked (no blue box). Note: this addresses Intellisense (not performance)