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?
Related
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?
In visual studio 2013 Web load testing has changed. It was working fine for a long time. But lately when I run a test, all of the Page Response Times are "nothing" and under Controller and Agents I'm getting a red X every time, and Processor Time shows Error. Can't figure out why or what's changed.
Image
Oops, my bad. Just realized the .webtest was empty. It didn't record in IE 11 because the web test recorder help add-in wasnt enable in IE11.
I'm working on a big code project. When I try to run a unit test in debug mode using nunit on Visual Studio 2013 Ultimate, there's a consistent 40 second delay before the test runs. Now, once the test starts running, it runs as fast as I'd expect. And if I run the test in Release mode, there's no delay.
I know it's a local environment problem because other developers report no similar delay when they fire up a test on the project.
I've been unable to determine what's causing this delay. The only visual evidence is that the cursor changes to a spinning cursor. I've disabled everything in Options that looked like it might be demanding. I have NCrunch and Resharper installed, but both are disabled, so neither appears to be at fault.
Any suggestions?
I'm getting a frustrating error when debugging in Visual Studio 2010.
I'm fairly certain that its something to do with a setting on IIS but no idea what it is!
here is the error:-
'The Web server process that was being debugged has been terminated by IIS.'
The time-out happens every time I debug, on any of the various workspaces we have at work
takes about 90 seconds of inactivity on the debugger for the error to show
IVE FOUND THE SOLUTION
In the advanced application pool settings in IIS you can change the maximum ping response time on the process model to stop the debugger timing out.
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