Ive been using nCrunch for years and am a huge fan. Recently changed project and trying to make my nCrunch run on VS 2022, running on Mac but Win10 environment (Parallels) and am getting the following exception when enabling nCrunch on the solution:
Unable to load component: System.IO.IOException: The path '' could not be processed because it is not of legal form
at nCrunch.Common.IO.DiskPath..ctor(String absolutePath, Boolean pathIsChecked)
at nCrunch.Common.IO.DirectoryPath.FromAbsolutePath(String absoluteFilePath)
at nCrunch.Client.ComponentLoader.SnapshotComponentFactory.(DirectoryPath )
at nCrunch.Client.ComponentLoader.SnapshotComponentFactory.CreateComponentsFromXml(FilePath projectFilePath, BuildXml projectXml, FilePath solutionFilePath, String[] additionalFilesToIncludeAtSolutionLevel, Boolean isLoadedFromFile, VisualStudioVersion vsVersion)
at nCrunch.Client.Initialisation.ProjectLoadInitTask.Run()
This is following a build error on all projects in the list.
Any idea if there is a config button I can adjust to make this message go away?
It looks to me like there is invalid data (i.e. a null project file path) being fed into the engine.
I'm not really sure how it's possible that this can happen. Does it happen on every solution? If you create a new sample project with one of the standard VS project templates, does the problem occur?
Looks like new solutions and projects works fine.
Seems to be something with this old one that Im currently looking at. Old .NET 451 with some issues around non-maintained packages. Could be part of the problem.
stenjo wrote:Looks like new solutions and projects works fine.
Seems to be something with this old one that Im currently looking at. Old .NET 451 with some issues around non-maintained packages. Could be part of the problem.
Could you submit a bug report after you've had this happen? I'm hoping the log file might yield some clues as to why this is happening.
It looks like the issue is caused by attempting to open the solution over a UNC path. Could you try mapping a network drive to the remote path and opening it from the mapped drive instead?