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

Notification

Icon
Error
NCrunch fails to build
Options
Previous Topic Next Topic
oneillci
#1 Posted : Sunday, December 4, 2011 3:58:34 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 12/4/2011(UTC)
Posts: 5
HI,

I've just installed NCrunch in a new MVC project ( File -> New Project and the default tests provided). I have changed the default MVC3 tests to use xUnit instead of MSTest. The 2 default tests fail to run with the following output:


System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at nCrunch.Core.ProcessManagement.ExternalProcessManager.#=qRkm8M2WYio3_BU5lSMVAtg==(Nullable`1 #=qLvrVKkCB6_Ic6YUqiPUfAnxQ$tA9xzO09lyG0vLO8eA=, Nullable`1 #=qDJJzsuRYnJ8gfj30qwUQHzX3CzHzxu3gCyl3XJY3ndo=, Type #=qLycDiplL_PvWMH0njSUSxA==, String #=qKYKWAAF1NY1YX6tbO5h8V9m4MyjWlce$RO6$KgIFmsg=, String #=q7h2rE_Q7CHeAqzlAN$AT5g==, String #=qJQmUtDehcNRpAV4SsvJmgoZnfKXCNCa9f84AUP5Z2Vg=)
at nCrunch.Core.ProcessManagement.ExternalProcessManager.LoadExternalProcess(ProcessLoadParameters parameters)
at nCrunch.Core.BuildManagement.BuildProcessLauncher.#=qfO4zMrAChS8R_IQWnfyYjpeef3BvuspR0sBt6_2$6Ggx6S5B0z9zKeG0G3jWnY0Y(Action`1 #=qzby81Gl79jMNsZ2ydluulw==)
at nCrunch.Core.BuildManagement.BuildProcessLauncher.AnalyseComponentBuildInExternalProcess(String projectFilePath, String buildXml, String useBuildConfiguration, String solutionDir)
at nCrunch.Core.ComponentLoader.SnapshotComponentFactory.#=qhzH3fDgeMQNy$Q7f19YshrzzdhorlM05yRGA_P$fQ6c=()
at nCrunch.Core.ComponentLoader.SnapshotComponentFactory.CreateSnapshotComponentFromXml(String projectFilePath, String projectXml, String solutionFilePath)


Is there anything I need to do to get it working correctly?

Thanks,
Ciaran
Back to top
Remco
#2 Posted : Sunday, December 4, 2011 5:16:44 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,140

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
This happens when NCrunch is unable to access/find its taskrunner executables. The most common cause is if something went wrong during the install process. Does doing an uninstall/reinstall of the 1.35b solve this problem?
Back to top
oneillci
#3 Posted : Sunday, December 4, 2011 6:37:07 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 12/4/2011(UTC)
Posts: 5
I've tried re-installing but no luck. Perhaps it's a conflict with another extension? I have Telerik JustCode installed, so I don't know if that would be an issue. Do you output any debug/trace files I could sent on to you?
Back to top
Remco
#4 Posted : Sunday, December 4, 2011 10:25:19 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,140

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
You can submit a bug report using the NCrunch menu - this contains a trace log showing the workings of the engine leading up to the error .. this will help to figure out what's going on.

Is this the first time you've used NCrunch? If not, has it worked for you before?

Also ... can you check whether the task runner .exes are sitting in your NCrunch install directory? You should be able to see the following exes:

nCrunch.TaskRunner20.x86.exe
nCrunch.TaskRunner40.x86.exe
nCrunch.TaskRunner20.x64.exe
nCrunch.TaskRunner40.x64.exe

In the directory: Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Remco Software\NCrunch for Visual Studio 2010
Back to top
oneillci
#5 Posted : Monday, December 5, 2011 8:55:53 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 12/4/2011(UTC)
Posts: 5
I have submitted a bug via the NCrunch menu with the title 'NCrunch fails to build - oneillci forum post'

This is my first time using NCrunch

The task runner exes are in place in the install directory.
Back to top
Remco
#6 Posted : Monday, December 5, 2011 10:05:20 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,140

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Thanks for sending through the report. It looks as though Visual Studio is loading the NCrunch Taskrunner.dll file from a shadow copied location. This is really wrong.

Try removing the contents of the User\AppData\Local\assembly directory - hopefully this will kick it to start using the proper installation instead of resolving to the wrong place.
Back to top
oneillci
#7 Posted : Monday, December 5, 2011 12:06:41 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 12/4/2011(UTC)
Posts: 5
I still get the same error after deleting User\AppData\Local\assembly. I have submitted another bug report.
Back to top
Remco
#8 Posted : Tuesday, December 6, 2011 4:12:59 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,140

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Thanks. If you remove the Local\assembly directory, do you still receive the problem if you immediately try NCrunch with a non-MVC solution (i.e. just a simple class library on its own) with any other test framework?
Back to top
oneillci
#9 Posted : Tuesday, December 6, 2011 12:44:09 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 12/4/2011(UTC)
Posts: 5
Very strange. I created a console app with a MS Test project, NCrunch ran fine.
Created a new MVC project, NCrunch ran fine.
Changed to use Xunit, NCrunch ran fine.
But it is still not working in my original project - while not 100% new, it's just got 1 new Controller and a few Actions and runs perfectly :/

NCrunch looks like great stuff though - will make my TDD workflow so much easier :)
Back to top
Remco
#10 Posted : Tuesday, December 6, 2011 8:30:25 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,140

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
I wonder if this could be related to the configuration file you're using on the MVC project. I've tried the default MVC3 templates at my end and they didn't cause this problem, but I have had a user before mention a similar sounding problem that they solved by deleting their config files...

I should be able to introduce a speculative fix to solve this problem in the 1.36b build, though I'm still curious as to why it is happening for your MVC project. I'd be interested to hear if removing your config file from the project resolves the problem.
Back to top
Remco
#11 Posted : Monday, December 19, 2011 8:10:54 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,140

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
The fix for the above problem has now been released as part of 1.36b.
Back to top
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.068 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download