"file is locked" when visual studio executes unit test - visual-studio

I developed near 300 unit tests, but sometimes, when trying to develop new tests, or just execute old tests, I got below error (for some of assemblies):
Could not copy "X.dll" to "bin\Debug\X.dll".
Exceeded retry count of 10. Failed.
The file is locked by: "Microsoft Visual Studio 2019 (37736)"
After that only restarting visual studio resolves problem. Normally this error will be thrown when I changed tests or library and try to execute test again.
Any idea how can I resolve this error?

Related

Build error in Visual Studio Community 2017

Start debugging. During debugging unhandled exception was thrown.
Stop debugging.
Edit code, start debugging with build, and build error appears
I think Visual Studio don't release these files after first debugging.
This error can appear even if exception wasn't thrown, but if debugging was just stopped.
How to fix it?
I think the best and quickest way is to close VS and kill all VS related processes in Task manager.
Try cleaning and then building your project instead of just building your project

Visual Studio load test error

I am using visual studio 2013 loadtest and I have a weird problem. I have 5 agents and 1 controller. After about a day of testing, there is always a socket exception in some of the agents. I can live with a simple disconnect after a day, but instead of disconnecting the tests continue but don't run my plugin anymore causing the load test to have no worth. Any ideas?

MS Unit tests fails run half of the time

I got this odd behaviour I launch tests from MS Test List Editor.
And first time I launch I always get this error currently
Error 11/15/2011 4:28:32 PM Failed to queue test run 'USER#MACHINE 2011-11-15
15:28:29': Unable to start program 'C:\Program Files (x86)\Microsoft
Visual Studio 10.0\Common7\IDE\QTAgent32.exe'.
Next launch is fine
I reproduced it 40 times already. Just as if first launch is clearing way for second one.
What could be the cause?
As Hans pointed out its a known issue.
http://connect.microsoft.com/VisualStudio/feedback/details/536475/launching-unit-tests-in-debugger-fails-every-other-time-cannot-start-qtagent32-exe
Its hard to reproduce and in my case I was able to fix it by reloading VS 2010.

A first chance exception of type 'StructureMap.StructureMapException' occurred in StructureMap.DLL

Hello I'm getting this exception thrown at me whenever I try to test a web application via visual studio, any ideas why? I'm building a project using MVC3 model and visual studio 2010
Exception: A first chance exception of type 'StructureMap.StructureMapException' occurred in StructureMap.DLL
First chance exceptions might occur while debugging. They might be handled properly by your code and never propagate when running the application normally but nevertheless Visual Studio shows them in Debug mode. If you don't want to be bothered you could disable them in Visual Studio and they will no longer appear.

How to increase timeout for activating features through Visual Studio deployment

I get the following error sometimes when deploying a SharePoint 2010 solution via Visual Studio 2010:
Error occurred in deployment step 'Activate Features': A timeout has occurred while invoking commands in SharePoint host process.
It's true -- it's taking a long time because we do a lot of work in the feature receiver. But This is not an error; I would just like Visual Studio to wait longer. Is there a place I can configure the amount of time to wait before timing out?
ChannelOperationTimeout
http://msdn.microsoft.com/en-us/library/ee471440.aspx
Do not forget to restart Visual Studio

Resources