Remco wrote:When you say that the directory was missing, do you mean the SalesQuotasViewModelTest directory, or the entire workspace?
Sorry, I can't answer that. I assume, the folder 330 was missing as this was the case with the missing xunit.dll but I can't say for sure as I haven't checked that in depth. I could check tomorrow at work, but I don't know if this will help as I have since resetted NCrunch.
[16:45:50.5788-BuildTask-168] ERROR (Internal): System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\daniel.hilgarth\AppData\Local\NCrunch\16368\84\GA.CoreData.UnitTests\SalesQuotas\SalesQuotasViewModelTest\ShownWeeks.cs'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode)
at nCrunch.Core.ProjectItems.SnapshotComponentMember.#=qRXf4UTRNcH1z5jIylzMoCAnFb2Tcmmdfhm21$Uud1PE=(String #=qIDcl4VGF5QsNDCrrEFo01w==)
at nCrunch.Core.ProjectItems.SnapshotComponentMember.WriteToFile(String fileToWriteTo)
at nCrunch.Core.WorkspaceManagement.WorkspaceBuilder.#=quyOMvjuRjJLlg$bsXV0j8WyvVbLWOkwSAug9mW9bjTY=(SnapshotComponent #=qDCuRCNUMnw5lOdfyM$WBrQ==, Workspace #=qjHvwLlb3x$Zum_vmRr9nrg==)
at nCrunch.Core.WorkspaceManagement.WorkspaceBuilder.UpdateExistingWorkspaceForComponent(SnapshotComponent component, Workspace& workspace)
at nCrunch.Core.WorkspaceManagement.WorkspaceManager.GetWorkspaceForComponent(SnapshotComponent snapshotComponent)
at nCrunch.Core.BuildManagement.BuildEnvironment.Build(SnapshotComponent snapshotComponentToBuild, IList`1 referencedComponents)
at nCrunch.Core.BuildTask.DoProcessTaskAndReturnSuccessFlag()
at nCrunch.Core.Processing.ProcessingTask.ProcessTaskAndReturnSuccessFlag()
at nCrunch.Core.Processing.ProcessingQueue.#=qmw8TP7OZQi1Awa12Usj2mw==(ProcessingTask #=qbasxLAEC$whviXkzL8WKzA==)
This time I verified that the complete workspace is missing, there is no folder 84.
The file ShownWeeks.cs is again a file I have added a few minutes earlier. After that NCrunch executed the test in that file for a few minutes before the above error occurred.
This is essentially an early build of the 1.43 release that I'm hoping to push out next week, as such, it contains a number of other fixes and optimisations that you may find useful. In an effort to resolve the problem you've reported above, this build contains a change to help strengthen some of the workspace handling.
I've also increased the captured log file to 10 times its normal size, as you've been reporting a large number of intermittent problems that appear to be symptoms of something going wrong much further in advance (and out of range of the normal bug report logs). You may notice a slight increase in memory consumption as a result of the extra logging, and any reports you capture will be significantly larger.
My hope is that this build will solve the problem you've described above, or at the very least will provide me with more information in order to reproduce and resolve it.
Thanks for the build. However, I fear we have a little problem here. My trial will expire in two days and version 1.42 was too fragile for me, as you surely noticed. It actually cost me more time than it saved, so to be honest, I am not yet prepared to pay for a license.
Furthermore, next week will be the last week before three weeks of christmas holiday [yeah! :-)], so even if you would be willing to extend the trial phase by another 30 days it would gain us only one additional week of testing.
Hm, I guess I know why: xunit.dll and xunit.extensions.dll were missing in c:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Remco Software\NCrunch for Visual Studio 2010\Xunit\Latest\.
1.43 contains a modification that disables navigation to source files that exist within the NCrunch workspace. Are the links themselves pointing to files within workspaces, or to your foreground solution? If they're pointing at the workspace, this is intended behaviour .. if they point at the foreground solution and they don't work, then this is definitely a bug.
Regarding the Xunit issue, did you at any time update your xunit binaries while using the previous version?
I'm sorry about the problems you've experienced with 1.42. I hope you have a great Christmas break and I wish you all the best.
Remco wrote:1.43 contains a modification that disables navigation to source files that exist within the NCrunch workspace. Are the links themselves pointing to files within workspaces, or to your foreground solution? If they're pointing at the workspace, this is intended behaviour .. if they point at the foreground solution and they don't work, then this is definitely a bug.
I saw that thread regarding this and checked the paths in detail. They were pointing to my solution, not to the NCrunch workspace.
Remco wrote:Regarding the Xunit issue, did you at any time update your xunit binaries while using the previous version?
Thanks for sharing the navigation issue. It looks as though one of the changes in the 1.43 release introduced a regression here. I've included a fix for this in the full 1.43 release that just went out the door (available on the download page).
I have a feeling that updating the xunit binaries in your NCrunch installation caused the MSI installer to fall out of alignment and create a problem here. I think the best way to resolve this is to follow the uninstall/reinstall instructions to create a clean setup, as simply placing the binaries back in manually will likely cause this problem to happen again the next time you upgrade.