When I build my project, Visual Studio 2015 takes forever, with the status bar looking like this:
The icon is animated: the arrow moves down, while the little boxes fall into the open square. If I had to guess, this would mean VS is trying to download something (packages?) but gets stuck somewhere. What does this icon mean, exactly? What does Initializing mean?
This is a Visual C++ project that built fine in Visual Studio 2013, but I'm moving to VS2015 because I needed noexcept. It uses SFML, but I've already replaced the library files with the Visual C++ 14 (2015) - 64-bit version.
I found and terminated a lingering Visual Studio 2013 process that still had the solution open -- this solved the problem. (In retrospect, I should have just rebooted!)
Question is to old but maybe my answer will be useful for someone in 2023. To make work correctly the animated icon On Visual Studio 2022 you need to disable the option shown on the screen (if you disable second one also the animated icon will disappear at all):
Related
I am experiencing this weird problem with Visual Studio 2022.
I created the skeleton of a new web application using individual accounts.
I have run the first migration, created some default accounts in the aspnet identity tables and
finally launched the application to test if everything was correctly setup in my PC.
Visual Studio compiles the application without problems and launch the defaul browser (Edge).
The standard Welcome page appears but immediately Visual Studio pops to the front doing nothing.
No errors, no messages nothing wrong. Just the code window here to obscure the browser window.
Now, I switch to the browser window and click on the Login link.
Again, the login window briefly appears in the browser but it is immediately obscured by Visual Studio.
Switch again to the browser, compile the required fields and click on login.
Again Visual Studio thinks that he is the best app on the planet and brings itself on the foregroud.
I have tried to switch to another browser, but the results are the same.
I have tried with an existing application written with Visual Studio 2019, but again the "pop in front of everything" still happens.
I have tried to search for this problem but probably I haven't find the right keywords to represent this problem correctly to a search engine.
I think that probably I have something wrong in the Visual Studio configuration, but it is practically impossible to find something there if you don't know what to look for.
The only option that seems to be related is "Bring Visual Studio to the foreqround when breaking in the debugger" but even after uncheking the option the "pop to front" persists.
So my question is simple. Has anyone experienced a similar behavior? If yes how have you fixed it?
Well, probably this situation is so messed that none will ever see this post.
Nevertheless I would like to share how I have finally resolved the question and leave here a warning for future readers.
The cause of Visual Studio 2022 hiccups is, probably, the import of Visual Studio 2019 settings.
I thought that it was a good idea to set 2022 with the same options used in the last 3 years so, after installing VS 2022
I used this very useful menu (Tools->Import Export Settings) to export all the Visual Studio 2019 Settings in an XML file and I reimported it in 2022.
I thought, if the file is not compatible with VS2022 surely it will abort the import. Right?
No, Visual Studio 2022 doesn't complain during the import of 2019 settings.
But something in that exported file should be very broken.
I have resolved the problem with these steps
Close Visual Studio 2022
Open a command prompt window with administrator rights
Change to the install folder for Visual Studio 2022 and then change dir to subfolder "Common7\IDE"
Finally execute the command
devenv /ResetSettings
After this everything started to work as expected without problems.
I have saved the broken VS2019 setting file and tried to compare it with one produced after the reset,
but they have too many differences to extract something useful to identify the specific problem area
I have recently downloaded visual studio 2022 for use in Unity and it was working correctly for a while, but today it has stopped auto-completing certain method names such as OnMouseButtonDown() and OnTriggerEnter2D(). Other methods such as Start() and Update() do work, but a majority of Unity specific methods are no longer auto completed. I've tried restarting visual studio code, restarting my computer and uninstalling and reinstalling visual studio code, but the error still persists. Any help would be greatly appreciated. Thanks.
This problem can cause various of reasons, even some IDE bug (which Visual Studio 2022 has a large number) but there is pretty common solution for this one
Firstly you'll have to make sure, that your Game development with Unity workload is checked
So
Open Visual Studio Installer and click Modify button across your version of Visual Studio.
Click on a Workloads panel and make sure that Game development with Unity workload is checked as shown on the image
Click Modify button at the bottom right corner.
Then you need to ensure, that desired version of Visual Studio is set as a External Script Editor inside Unity engine
Open Unity
Edit -> Preferences -> External Tools
And make sure that External Script Editor set as a current version of like so
Click on Regenerate project files button and try to always open your scripts directly from Unity
Restart Unity after those steps
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'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.
Until quite recently it was possible to click on a method in the VS 2013 Solution Explorer and have the method appear in the code window. That does not appear to be working anymore. Any idea of how to enable this functionality? It was quite useful. For example, in the Solution Explorer view below, clicking on either addBlanks or formatSql would move the code window to the method in question.
It turns out that I have more information about this problem. I completely uninstalled VS 2013 Pro and reinstalled it. Somewhat predictably the problem went away... However, I was getting an error message about the NuGet package manager not being properly installed. To fix this I removed and reinstalled the NuGet package manager. That did resolve the NuGet error message, but the problem with clicking on methods in the Solution Explorer came back. Finally I removed and reinstalled VS 2013 Pro yet another time and now clicking on methods in the Solution Explorer works correctly.
Somehow the original problem reflects some combination of VS 2013 Pro, NuGet, etc.
It is still possible to quickly display a source code file. I am using Visual Studio 2013 Express Update 3.
It might make a difference to highlight/activate the right-most code preview symbol in the Solution Explorer panel:
It is located to the right of the properties screw-wrench symbol.
If this symbol is active, a single click on a file name is sufficient to get the file displayed in the code view. The same applies to methods. Double-click also works, when the preview symbol is not highlighted.
This turned out to be a bug in Visual Studio 2013 Pro Update 3 (and perhaps other versions). Microsoft recognized this bug and has fixed it in VS 2013 Pro Update 4. See https://connect.microsoft.com/VisualStudio/feedback/details/1001072/double-click-in-visual-studio-2013-update-3-solution-explorer-not-working for a discussion and Microsoft's resolution.