Everything was working fine with my Visual Studio (Ultimate 2013) today until I came back from lunch and I started getting CPU spikes every time I switch between tabs within Visual Studio (Ultimate 2013). It especially appears to be happening when I switch between config files.
Using Process Monitor, I was able to determine that it was continually searching in the packages folder:
For the same things over and over again:
How do I keep VS from doing this?
Go to Tools --> Nuget Package Manager --> Manage Nuget Packages For Solution...
It will prompt that not all packages have been downloaded. Select that you'd like to download them.
Problem solved.
Related
Our IT department had to reinstall my work PC.
After receiving it back, I installed Visual Studio 2017. Added the NuGet Package Sources that I needed as well as installed the EPiServer CMS Extenion for Visual Studio.
I restarted the computer.
However when I launch our EPiServer project in Visual Studio, and look at my code, I see that all the using EPiServer; directives show up as being unused as well as are underlined with a red line.
In my code, any reference to code from these using directives is also red underlined.
Before the reinstallation of the operating system I had a similar setup of Visual Studio where these using statements worked.
It appears all I had to do was build the project once right after setting everything up.
After having built the project, now when I browser the various .cs files, the using statements are showing up correctly as being used where relevant.
When calling devenv.com from command line or FinalBuilder action within our automated build it sometimes hangs and never gets past compiling step.
It is called with this parameters from C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE:
devenv.com /build "Release|Any CPU" "D:\MyProject\MySolution.sln"
It hangs forever on this step. When I open it in VS 2013 and ReBuild the solution it works fine every time.
Any ideas? I've also tried it on other build machines and it does the same. So it is not machine dependent.
After a lot of troubleshooting and looking through various logs, solutions, googling, I figured out that this is caused by the Extension Manager in Visual Studio 2013.
You can find the extension manager in all Visual Studio version -> Tools -> Extensions and updates.
So by uninstalling the Nuget Package Manager from Visual Studio 2013, made it the solutions compile successfully every time.
Another fix we noticed and could reproduce every time is when our virtual machine in Hyper-V was given 2 CPUs, it would cause builds to hang every time. Reducing the VM to only have 1 CPU fixes the problem.
We have solved this by creating a new .sln and adding existing projects to it. NuGet info is now revomed from the .csproj files and we now use "nuget.exe restore" to update NuGet packages before a call to devenv.com. This has fixed it for some projects.
I have several SSIS packages that were created and can be opened using Visual Studio 2010 with Integration Services. I have read in many locations that newer versions of Visual Studio can open these files. I have Visual Studio 2013, so I installed SQL Server Data Tools-Business Intelligence, and tried to open the solution with the SSIS project, which worked--but then, it tried to upgrade the packages, and gives me this error:
Failed to migrate scripts contained in the package to the VSTA 11.0
format. Move the scripts to a new Script Component.
Is there any way to edit the package "the old way" in VS2013, without upgrading/migrating the package?
How do I obey and do what it asks me to do? I can't find instructions anywhere. MSDN is unhelpful.
Can I install SQL Server Data Tools-Business Intelligence for new instances of Visual Studio 2010, so that others can edit these packages without upgrading them? It seems like the installers are gone.
No, none that I know of
Once the automatic upgrade has finished. You open each package with scripts. Open each script task/transformation. Recompile. Save. And Close.
Not that I know of.
This has worked for me upgrading from 2008 to 2012 and I think also applies to 2010 to 2012/3
Note that I think once you've upgraded the package - VS2010 should still be able to work with the package, but if you install the SSDT-BI for VS2013 then this will install the VS2013 Shell (enough to edit the packages) even if you don't have the the full VS2013 available.
Edit:
Do you have SQL Server 2012 SP2? I've found an issue with SSIS packages using VSTA on SP2 in that they won't open (ie. the designer won't open) and also they fail at run time. At this stage I've gone back from SP2 to continue working.
I am running VS 2013 ultimate on win 8.1 Parallels and everything was working fine, now does not. I have repaired the install, and have even uninstalled and reinstalled VS 2013. WHen I run devenv.exe the initial VS loading screen shows and just spins. When I look at Task Manager, I only see VS running as a background process and eating up the CPU.
When I select a solution file or xml file as an example and choose the VS 2013, VS comes up and loads the file. Any ideas of how to get this working would be GREATLY appreciated.
I was able to get the IDE to come up in safemode, so I figured it was one of the third party addins. It seems like the Productivity Power Tools addin was the culprit in my situation.
I'm using Visual C# 2010 Express RTM with Windows Phone Developer Tools April CTP Refresh and when I run any Build option, nothing happens. I've deleted the contents of the build output folders and that doesn't do anything. I can't even run the project, because it complains the executable is missing (XNA Game for Windows project). I've tried the project on another computer and it builds just fine. Any ideas?
I'm not sure how this happens, but here's how I fixed it:
Open Build -> Configuration Manager
In the "Platform" column, choose x86 instead of Any CPU
Click close
These exact steps may not work for you, but I've found that if you play around in the Configuration Manager window it will usually resolve this problem.
try a reinstall?
Visual Studio 2010 doesn't work with current versions of XNA Studio. You'll could wait until XNA Studio 4 comes out (apparently due this month).
To solve your issue, use Visual Studio 2008 or use the workaround at this link to continue using VS2010 and XNA.