Daily Usage Issues

Renaming Test Library

Started by Mark on 7,020 views

I had an issue this morning where NCrunch would refuse to build my test project even though directly building it in visual studio worked fine. I believe what happened is that when I renamed the test project, NCrunch must have held onto an old reference of the project and been using that to build. I noticed that the build failure in NCrunch was calling the project by the old name. I disabled and reenabled NCrunch and it appears that it grabbed the new reference because now the project builds fine and in the tests list, it has no mention of the old name anymore.

If this isn't clear let me know maybe I can reproduce it in a sample project but I'm hesitant because if you open my sample project with the error it'll probably work due to NCrunch reinitializing when you open the project.
Hi Mark -

Thanks for reporting this. I'm eager to try and gain some steps to reproduce this problem. Does it happen for you consistently when you rename projects? If you can get it to happen again, try submitting a bug report - the log file may help me to find out why the engine has messed itself up.


Cheers,

Remco
Hey Remco,

I went ahead and tried reproducing it on a simple 2 library project and was unable to do so. Basically the majority of my debug session was moving files between projects, updating namespaces and changing references between projects to fix errors as I changed what was in which namespace. I guess this will just have to be one of those issues I'll keep an eye out for and if it happens again maybe I'll figure out some new details.

Thanks,
This was probably caused by a race condition of some kind. Do let me know if you manage to find a way to reproduce it.


Thanks!

Remco

Post a reply

Log in to reply.