ENGINE - [10:21:51.4127-InitialisationQueueTask-76] ERROR (Load): Error occurred during load of component at
UnitTests.csproj: System.Exception: An exception was thrown in the remote environment: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> nCrunch.Common.UserException: Errors occurred while trying to load the project file:
The "ResolvePackageAssets" task failed unexpectedly.
NuGet.Frameworks.FrameworkException: Invalid framework identifier ''.
at NuGet.Frameworks.NuGetFramework.GetShortFolderName(IFrameworkNameProvider mappings)
at Microsoft.NET.Build.Tasks.LockFileExtensions.GetTargetAndThrowIfNotFound(LockFile lockFile, NuGetFramework framework, String runtime)
at Microsoft.NET.Build.Tasks.ResolvePackageAssets.CacheWriter..ctor(ResolvePackageAssets task)
at Microsoft.NET.Build.Tasks.ResolvePackageAssets.CacheReader.CreateReaderFromDisk(ResolvePackageAssets task, Byte[] settingsHash)
at Microsoft.NET.Build.Tasks.ResolvePackageAssets.CacheReader..ctor(ResolvePackageAssets task)
at Microsoft.NET.Build.Tasks.ResolvePackageAssets.ReadItemGroups()
at Microsoft.NET.Build.Tasks.ResolvePackageAssets.ExecuteCore()
at Microsoft.NET.Build.Tasks.TaskBase.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext()
at nCrunch.Compiler.ComponentAnalysisContext.()
at nCrunch.Compiler.ComponentAnalysisContext.AnalyseComponentBuild()
at nCrunch.Compiler.RemoteBuildRunner.AnalyseComponentBuild(ComponentLoadParameters parameters)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at nCrunch.TaskRunner.Ipc.IpcMessageProcessor.(CallMethodMessage )
at nCrunch.TaskRunner.Ipc.IpcMessageProcessor.ProcessMessageReturningResult(Byte[] data)
at nCrunch.TaskRunner.Ipc.RemoteInstance.(Byte[] )
at nCrunch.TaskRunner.Ipc.RemoteInstance.Invoke(IMessage msg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at nCrunch.Compiler.IRemoteBuildRunner.AnalyseComponentBuild(ComponentLoadParameters parameters)
at nCrunch.Core.BuildManagement.BuildProcessLauncher..(IRemoteBuildRunner )
at nCrunch.Core.BuildManagement.BuildProcessLauncher.(Action`1 , FilePath , String , ExternalProcess )
at nCrunch.Core.BuildManagement.BuildProcessLauncher.(Action`1 , EffectiveProcessorArchitecture , GridClientId , BuildSystemParameters , IList`1 , Nullable`1 , GridAddress )
at nCrunch.Core.BuildManagement.BuildProcessLauncher.AnalyseComponentBuildInExternalProcess(ComponentLoadParameters parameters, IList`1 customEnvironmentVariables)
at nCrunch.Client.ComponentLoader.SnapshotComponentLoader.(EffectiveProcessorArchitecture , String )
at nCrunch.Client.ComponentLoader.SnapshotComponentLoader.CreateComponentFromXml(FilePath projectFilePath, ParsedBuildXml projectXml, FilePath solutionFilePath, String[] additionalFilesToIncludeAtSolutionLevel, Boolean isLoadedFromFile, VisualStudioVersion vsVersion, ComponentUniqueName componentName, TaskSettings componentTaskSettings, Exception parseException, String targetFramework)

<PropertyGroup>
<TargetFramework>$(AppFrameworkVersion)</TargetFramework>
</PropertyGroup>

<Project>
<PropertyGroup>
<AppFrameworkVersion>netcoreapp3.1</AppFrameworkVersion>
<LibraryFrameworkVersion>netstandard2.1</LibraryFrameworkVersion>
</PropertyGroup>
</Project>

<ProjectConfiguration>
<Settings>
<CustomBuildProperties>
<Value>TargetFramework = netcoreapp3.1</Value>
</CustomBuildProperties>
</Settings>
</ProjectConfiguration>

Good morning!

We have a large number of c# projects and have been upgrading frameworks very quickly and it was very human error prone so we broke the target framework out into a property in our Directory.Build.props. I added the Directory.Build.props file to the ncrunch config to copy over as a needed file but still ncrunch gives me an error about unknown framework. For now I've explicitly defined the framework as a custom build property on every project but I'd like to remove that if possible. This appears to only be an issue with building in ncrunch as the rest of our build / deployment pipeline works. Does anyone have any ideas how to resolve this issue?

Ncrunch 4.2, optimized engine.

Thank you!



From csproj:


From Directory.Build.props


works if I override ncrunch with this

Yes. Unfortunately, under NCrunch the mechanics of our integration with the build system require us to know the target frameworks well in advance of loading the project. Thus we need to establish this by parsing the project files or via a configuration setting. Specifying target frameworks indirectly outside the project file would require us to rebuild the entire parsing logic of the build system, which just isn't feasible for us. So at the moment, if you specify your target frameworks in the directory.props, you must also specify it in your NCrunch configuration.

Are these multi-targeted projects? If not, there may be a fallback in place that can work for this situation.