I just recently mapped a project from TFS to my local. Whenever I try to open the solution, Visual Studios then "GETS" it from the server... every time!
Normally, this does not happen when opening a new solution.
Is there a reason why this might be happening? And how can I stop it?
Related
I am having a very weird issue. I am able to build my C++/CLR Win Forms project with visual studio 2017 only once. Every next time I am getting “LNK1104 cannot open file ….\Debug\….exe” error.
What I have noticed is that after stopping debugging the program is still visible in Task Manager which is I believe the reason of getting the above message.
When I try to kill it am getting “access denied”.
The only way to compile the project is to restart visual studio. The process shuts down immediately together with visual studio. Once the visual studio is back on I can do a single build again.
I have tried to run "clean" project and solution.
I have also created new project and moved my files in it. What I have noticed is that before having my form filled with controls the problem was not appearing. It started happening after adding few textBoxes, ListView and buttons.
Any ideas how to fix it?
I figured out what was causing the issue. I have tried with switching off multiple Windows security features and finally I found the right one. The problem appeared to be a Windows 10 built in "Real-time protection" against malware. It can be disabled under "Virus & threat protection settings".
Background
I maintain several web sites that are Visual Studio "Web Site Projects".
Problem
I've found that with a couple of these projects, Visual Studio regularly freezes while I'm working on the code. This doesn't happen for some of the web site projects, and I haven't seen it happen on any Web Application projects.
Symptoms
Each time it freezes, it takes about half a minute before I can use it again.
During a freeze, Windows Task Manager reports that Microsoft.VisualStudio.Web.Host.exe is maxing out one of the CPU cores.
Steps to Reproduce
Open a .cs file under the App_Code directory.
Make a change to the file.
Save the file.
Navigate somewhere else (eg switch tab, close the file, open different program in Windows).
Navigate back to the file (eg switch tab to it, open it, or go back to Visual Studio).
Other actions that sometimes seem to trigger the problem:
"Go to definition"
Opening a file
Previewing a file
Closing a file
Using a refactoring
"Find usages"
What I've Tried
Both Visual Studio 2012 and Visual Studio 2015
Changing the website project's build action
Disabling "Build Web site as part of solution"
Deleting web references and the Bin folder seems to minimise the problem, but obviously this breaks the web site. Maybe web site projects experience this problem when they contain a lot of C# code other than code-behind files?
Similar problems
I found the following potentially-related problems using Google, but none of them seemed to contain a workaround or solution.
Microsoft.VisualStudio.Web.Host.exe Time Theft
Microsoft.VisualStudio.Web.Host.exe
Visual Studio 2012 freezes for approximately 30 seconds after every build
I noticed that the problem happened less often when I suspended ReSharper.
The problem still happened occasionally when editing classes under App_Code, but restarting Visual Studio worked around it.
I was facing a similar problem. A single Web application project with dozens of class libraries, migrated over from VS 2010 into VS 2013.
I was able to solve my problem by disabling the "Hosting Process" option:
To disable the hosting process
Open an executable project in Visual Studio. Projects that do not
produce executables (for example, class library or service projects)
do not have this option.
On the Project menu, click Properties.
Click the Debug tab.
Clear the Enable the Visual Studio hosting process check box.
Full details on MSDN: http://msdn.microsoft.com/en-us/library/ms185330.aspx
Another option for people experiencing this on old web applications that don't have the properties page in the accepted answer above.
Disable "Allow this precompiled site to be updatable".
Open Site/Solution
Right click and view Property Pages
Go to MSBuild Options
Uncheck "Allow this precompiled site to be updatable"
This worked for me.
This problem stopped happening when the Web Site project was converted into a Web Application project.
Not an easy solution, but it did stop the problem.
They symptoms in the question of this post sound exactly like the nightmares I just had today:
Other actions that sometimes seem to trigger the problem:
"Go to definition"
Opening a file
Previewing a file
Closing a file
Using a refactoring "Find usages"
Plus intellisense wasn't working (even with CTRL + J) and
'Peek definition' was hanging as well.
I had to keep task killing visual studio (both 2015 and 2017).
My fix was to go into the project that I was having problems with, open the 'Package Manager Console' and uninstall and re-install the 'DotNetCompilerPlatform'
uninstall-package Microsoft.CodeDom.Providers.DotNetCompilerPlatform
and then
install-package Microsoft.CodeDom.Providers.DotNetCompilerPlatform
So far every problem I was encountering has not resurfaced (but this was just today so still need to give it time).
UPDATE:
It started creeping back again. I noticed also that whomever had installed to the solution had only done it to two of the various projects. Uninstalling the compiler platform (which means using the compilers that came with Visual Studio) has made life sane again.
I have problem with my visual studio. Something went wrong with my project properties and I always see everything disabled. It hapens even if I create new console application.
Any ideas? I restarted all visual studio settings, restarted computer, uninstalled extensions, searched the web but nothing helped.
I used Repair in add or remove programs and it is working fine now. Wonder what went wrong. I dont like this "it worked yesterday" problems.
The same symptom occurs while running your program in Visual Studio using the debugger.
If the project properties are greyed out, first check if you are debugging. If you are, finish debugging, then look again at the property pages.
After installing Visual Studio 2012 and opening/upgrading a Visual Studio 2010 solution from Team Foundation Server that contains two "website"-type projects I keep getting the message that "The project 'website' has been modified outside the environment" with the option to reload every time I add or remove a file to the "website" project.
This is odd, because as far as I know this type of project does not have a project file and thus it is impossible to edit it, in addition, nobody is editing anything outside of the environment.
Does anyone know what causes this and how to fix it?
To at least partially answer my own question. You can solve this by closing Visual Studio 2012 and then deleting the .suo file for the solution. It should be sitting right next to the solution file and has the same name.
After deleting this file I reopened the solution and VS2012 went to get the entire solution from TFS again. When it was done, the problem was gone!
At first I thought I was going mad, but now I know I'm not. I've only been using Visual C++ 2008 Express Edition for a couple of weeks, but I've found that I have had a problem that I just can't get around, but returning to the program the next day I find that the problem has disappeared.
For example, the last time I was using VC++ I couldn't get Build to output an exe file, but today it has no problem.
Has anyone else found this? I like VC++ but I'm only a beginner and I don't know when it's VC++ being stupid and when it's me!
I've had Visual Studio act up before. Usually it just involves the entire application hanging intermittently. Restarting the application usually fixes the problem.
If this does not fix it, you might try examining the build log to see what's going on, if you haven't already.
Visual Studio changes the menu items based on normal development or debug mode.
So you can't build your exe or do some other things while you're debugging. Unfortunately sometimes you simply forgot that you still have a debug session open somewhere.
Pressing Shift-F5 fixes this.