Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

VS = No Build Errors, NCrunch Many Build Errors
CoolBreeze
#1 Posted : Monday, April 3, 2017 9:28:14 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 7/11/2014(UTC)
Posts: 79
Location: United States of America

Was thanked: 9 time(s) in 9 post(s)
Visual Studio reports 0 build errors. NCrunch reports build failure and lists several VS error messages.



  1. I started with a VB project
  2. I moved several VB classes into a separate class library. Let's call it Planets.
  3. During the move I changed the names of some of the classes, properties, and methods.
  4. I successfully tested and built the Planets library.
  5. I came back to the original project, added a reference to the Planets project.
  6. Initially VS listed errors for those items I moved to Planets because the names didn't match anymore.
  7. I updated all the names to the "Planets" version of the names.
  8. I noticed VS listed errors for these new names, especially Enums even though the names were correct.
  9. As I clicked on the error in the VS Error List VS would remove the error.
  10. Eventually VS listed no errors in Errors List.
  11. I opened the NCrunch Tests window.
  12. NCrunch reports "1 project is failing to build".
  13. NCrunch appears to list the same errors that were originally in the VS Error List.
  14. I closed the NCrunch Tests window and disabled NCrunch.
  15. I enabled NCrunch and opened the Tests window.
  16. NCrunch still shows the VS build errors.
  17. I closed and restarted VS and opened Tests window.
  18. NCrunch still shows the VS build errors.
  19. I cleaned the solution and did a Rebuild.
  20. NCrunch still shows the VS build errors.
  21. Also, I see build errors in Processing Queue window.



Maybe I should try a reboot?


Versions:
NCrunch 3.6.0.2
Visual studio 2017 Community
Remco
#2 Posted : Monday, April 3, 2017 11:31:28 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,976

Thanks: 931 times
Was thanked: 1257 time(s) in 1170 post(s)
Hi Ed,

Thanks for sharing this problem.

Can you check if NCrunch has given you any warnings in the Tests Window? I wonder if this might be caused by a reference to an old assembly.

Deleting the _ncrunch directory with the IDE closed will completely reset the NCrunch state. This might be worth a try.
CoolBreeze
#3 Posted : Tuesday, April 4, 2017 11:57:04 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 7/11/2014(UTC)
Posts: 79
Location: United States of America

Was thanked: 9 time(s) in 9 post(s)
Hi Remco,

I had to go through 3-4 cycles of shutting down VS and deleting the _ncrunch directory and then restarting VS and NCrunch. But eventually, NCrunch didn't list any errors and finally listed the test projects and tests in the Tests window.

I did notice at one point VS showed errors which were not shown previously. NCrunch showed a bunch of other earlier errors. I cleaned up the new set of errors.

Also, I noticed the class library I was referencing, which I called Planets, in my original post was at ASP.NET framework 4.5.2 and my test project was at 4.5.0.

VS complained about the differences. I set Planets project to 4.5 and VS stopped complaining about the different versions.

Not sure if those two items were the cause of NCrunch showing those older errors.

Maybe VS 2017 has some internal build synchronization problem? I don't know.

I'll have to keep in mind the idea of deleting the _Ncrunch* folder to fix things up.

Thanks, Ed
Remco
#4 Posted : Tuesday, April 4, 2017 12:25:06 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,976

Thanks: 931 times
Was thanked: 1257 time(s) in 1170 post(s)
Hi Ed,

VS has an internal system designed to detect references from older frameworks to newer ones, and usually will try to warn you of this in some form or another. NCrunch doesn't have such a mechanism, so it's possible the problem was instead being kicked up in the form of MSBuild exceptions. I am uncertain of why the results weren't consistent here. Let me know if you find a way to reproduce this.
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.035 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download