There's several symptoms so I'll try my best to give as clear a picture as possible:
* I have a solution with 26 projects.
* My current focus is trying to run a test in the main test project with hundreds of tests.
* NCrunch Tests shows 4 tests.
* NCrunch Tests shows blue check next to the tets project.
* I right-click and select Reload and Rebuild...
* NCrunch changes blue check mark to green clock for 10-20 seconds.
* NCrunch returns to blue check mark.
* NCrunch still shows 4 tests and isn't showing all the hundreds of tests.
* NCrunch shows build warnings for the Test project, but no build errors.
* I cleaned and rebuilt the solution. Same behavior\symptoms.
* I disabled NCrunch and closed Tests window.
* I enabled and opened Tests window.
* NCrunch rebuilds all the projects. For the key test project it appears NCrunch works on building (green clock)
but then shows blue checkmark.
* I deleted the _Ncrunch folder for the main code project that the test project tests against.
* Same behavior\symptoms.
* My work environment was moved from a physical box to a virtual machine with same RAM allocation and more disk space.
* To rebuild entire solution takes 7-8 minutes. I'm not sure why longer for NCrunch to build projects.
* I did turn on the Trace setting as you suggested in another post. With updating a code mode and related test and then trying different things to get the test project to build I didn't have a chance to fully investigate the Trace information.
I'm stuck. I can't run my tests.
Remco NCrunch Developer
#10249
12 Apr 2017 00:13 UTC
Is there any chance you could submit a bug report directly after seeing this behaviour? (i.e. the green going to blue and staying there).
Also, what kind of project is this? (i.e. .NET Framework, .NET Core, netstandard, etc).
Also, what kind of project is this? (i.e. .NET Framework, .NET Core, netstandard, etc).
re: Also, what kind of project is this?
.NET Framework 4.0
VB
Visual Studio 2010
(some class libraries built in Visual Studio 2017, .NET 4.0)
I was able to run a test earlier in the day. But then ran into the problem described in my original post entry.
Will submit bug report Wed EST morning.
Ed
.NET Framework 4.0
VB
Visual Studio 2010
(some class libraries built in Visual Studio 2017, .NET 4.0)
I was able to run a test earlier in the day. But then ran into the problem described in my original post entry.
Will submit bug report Wed EST morning.
Ed
Remco NCrunch Developer
#10253
12 Apr 2017 06:18 UTC
Thanks! It's refreshing to know that other people are still using the older frameworks. Most of the problem reports these days are on the newer stuff (VS2017, .NET Core, .NET 4.6.2, etc). I still look forward to the day when I can upgrade the NCrunch core components to .NET 4.0.
I'll watch out for your bug report and will try to advise as soon as I have more information.
I'll watch out for your bug report and will try to advise as soon as I have more information.
Post a reply
Log in to reply.