I have a particular project that uses 100% of the CPU whenever it is open. You can see, below, the CPU is being used heavily by Visual Studio and Node. I have disabled several VS extensions but still have the problem. Also it continues even if I delete gulp.js, package.json, and bower.json files. It is a C# web project. This doesn’t happen with other VS projects on my machine.
Restarting Visual Studio doesn't help, but restarting my whole PC does make the problem go away, for a while.
I fixed this issue by upgrading from Windows 7 to 10. I chose the option to keep my existing applications; Enterprise edition; it went smoothly.
Related
I've Visual Studio 2017 community edition. I have a C# project created using Visual Studio 2015. When I try to open the project in VS 2017 I get an error message prompt:
--------------------- Microsoft Visual Studio
Project 'dataStructureInCSharp' could not be opened because the Visual C# 2017 compiler could not be created.
Please re-install Visual Studio.
--------------------------- OK
I'm trying to obtain help if anyone else has faced similar issue. I feel going the uninstall and then reinstall route is very costly for me and would try that option last if I've got no other resort.
What I've done so far :
Tried starting visual studio with administrative privileges
But problem remained same.
I tried creating a new console project solution from scratch but in that case I get very same error and an additional error error also shown below:
System Environment: Windows 7 Ultimate Service Pack 1
You can try to close all VS 2017 instances and delete the folder %localappdata%\Microsoft\VisualStudio\15.0_xxxx\ComponentModelCache, then open VS to create a new Console project.
Or
please re-run the VS 2017 installer as administrator, click the icon beside ‘Launch’ button and choose ‘Repair’ to repair as shown below:
Just to brief the history of my problem, I had first installed Visual Studio(VS) 2017 community when it was in RC stage. This was first time when I saw the workload based UI of visual studio installation. Initially I simply chose .Net desktop development workload to get started as I was interested in creating only console applications to get my hands dirty.
Initially it was all working well. One fine day I added all other workloads I was interested in namely Universal Windows Platform Development, Azure Development, ASP.NET and web development,Node.js development, and Mobile development with .Net. I'm not sure if there any of the specific workloads to be blamed for the issue I've posted.
Just to avoid the case if RC and RTM release builds might not have messed up my entire environment, I simply uninstalled the entire stuff, rebooted my machine and installed it again from scratch from latest RTM release for Visual Studio Community.
I would strongly recommend that you first try possible solutions suggested by #Sara-MSFT before doing clean reinstall just in case if it works. It can save you couple of hours required in whole reinstallation process if it works.
I have a legacy solution in C#, .net 1.1 and Visual Studio .NET. My solution consists on many projects. Once I run in debug mode my initial project, then I attach to other processes. When I try to attach to a process, Visual Studio IDE crashes and I need to start IDE again. It's a pain!
Anyone has some idea on how to get rid of this?
I'm not sure if there's a fix, but a way around it is to limit the number of processes you're attaching to.
Start with just connecting to one, then increase the number if stable.
To identify which project is running on each port you can run
IIS6
c:\windows\system32\cscript c:\windows\system32\iisapp.vbs
IIS 7
C:\windows\system32\inetsrv\appcmd list wp
Yesterday, I encountered the problem multiple times that Microsoft Visual Studio 2013 restart unpredictably when it loads very large C++ and C# solutions.
I researched Stack Overflow and found this particular article: Visual Studio 2013 hangs when opening a solution
which suggests deleting the suo files. However, when I tried that the problem persisted.
I also tried uninstalling and reinstalling Microsoft Visual Studio 2013 and still the problem persisted.
I then tried loading a smaller solution consisting of a C# solution and a C++ project and that succeeded in loading, compiling and linking.
I was wondering why I suddenly encountered this problem. Could the cause of the problem be related to the amount of 64 bit physical memory I have installed on my 64-bit desktop system? Alternatively, could it be due to a computer virus even though my desktop system has an antivirus package installed. We are tring to avoid reimaging the disk of my 64-bit desktop system and reinstalling all the software which could take 2 days to complete. Any help is greatly appreciated.
It's probably some plug-in misbehaving. You can try disabling them (Tools => Extensions and Updates) and experimentally determine which one is causing the issue.
If you want to go all-in, you can debug it:
Download and install WinDbg 32-bit
Run Visual Studio under windbg: windbg -g "%VS120COMNTOOLS%..\ide\devenv.exe" c:\my\solution.sln
Watch the incredible amount of debug info VS spews into
WinDbg
If Windbg breaks, inspect the stack - maybe some DLLs on it will clue you into which plug-in is the culprit.
Open file explore and past this command
'%AppData%..\Local\Microsoft\VisualStudio\12.0\ComponentModelCache'
Then remove 'ComponentModelCache' folder.
Restart the visual studio.
When i tried to created a WPF application it gets stuck on "Creating Project" and an error message occasionally pops up
"
Microsoft Visual Studio Express 2013 for windows desktop is waiting for an internal operation to complete. if you regularly encounter this delay during normal usage, please report this problem to Microsoft."
I've tried to search for answers and disable my antivirus but to no avail. Would appreciate any help.
I had the same problem while working on an ASP.NET project; the only thing that worked for me was building a new project and copying and pasting the code.
(It took a really long time to build the new project for some reason.)
Restart your VS and/or your PC. VS 2013 is incredibly faster than 2010 but still has many bugs.
I just jumped back into a project that previously had no issues. We just upgraded to visual studio 2012. This morning I open my project to work on my code. I am getting designer issues all over the place.
"If this type is a part of your development project, make sure that the project has been successfully built using settings for your current platform or Any CPU"
It all seems to be coming from this platform issue. I have had zero issues in the past. I cannot find any information on how to fix this. I even go to open the designer on a file that previously worked (pre VS2012 install) and that fails.
So I went back to VS2010...without changing anything and attempted to open the same designer on the same file that previously worked and I also get an app crash.
Did somehow my visual studio 2012 install cause all of this?
Make sure that you are choosing the right CPU architecture for your designer. If it is ARM then you might see that message. You can check your CPU settings for your project like this: