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

Notification

Icon
Error
NCrunch Console on dotnetcore without vstudio2017?
Options
Previous Topic Next Topic
GreenMoose
#1 Posted : Tuesday, March 21, 2017 12:24:24 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 6/17/2012(UTC)
Posts: 507

Thanks: 145 times
Was thanked: 66 time(s) in 64 post(s)
Hi,

Trying out ncrunchConsole on a TeamCity agent, not having vstudio 2017 installed. The plan is to build dotnetcore projects first of all.
Is this possible or must I have vstudio2017 installed, or is sufficient with https://blogs.msdn.micro...ual-studio-build-tools/ ?

When currently just trying the console app on my solution on the build agent I get popups like below
Quote:

nCrunch.BuildHost462.x86.exe - This application could not be started.
This application requires one of the following versions of the .NET Framework:
.NETFramework,Version=v4.6.2

Do you want to install this .NET Framework version now?
Yes No
Back to top
GreenMoose
#2 Posted : Tuesday, March 21, 2017 1:18:17 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 6/17/2012(UTC)
Posts: 507

Thanks: 145 times
Was thanked: 66 time(s) in 64 post(s)
Well, installing build tools 2017, net famework 4.6.2 and then rebooting didn't really help:
Quote:

[14:15:56.706-InitialisationQueueTask-8] ERROR (Load): Error occurred during load of component at D:\TeamCity\buildAgent\work\....NUnitTests.csproj: System.Exception: An exception was thrown in the remote environment: System.Reflectio
Exception: Exception has been thrown by the target of an invocation. ---> nCrunch.Common.UserException: Errors occurred while trying to load the project file:
The target "_SplitProjectReferencesByFileExistence" does not exist in the project.
at nCrunch.Compiler.RemoteBuildRunner.☻(FilePath ☻, LoadTimeQuery ♥, String ♣, String, DirectoryPath ♠, String ♫, String ☼)
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 ☻, ProcessorArchitecture ♥, GridClientId ♣, BuildSystemParameters, IList`1 ♠)
at nCrunch.Core.BuildManagement.BuildProcessLauncher.AnalyseComponentBuildInExternalProcess(ComponentLoadParameters parameters, IList`1 customEnvironmentVariab
at nCrunch.Client.ComponentLoader.SnapshotComponentLoader.☻(ProcessorArchitecture ☻, String ♥)
at nCrunch.Client.ComponentLoader.SnapshotComponentLoader.CreateComponentFromXml(FilePath projectFilePath, ParsedBuildXml projectXml, FilePath solutionFilePath
nalFilesToIncludeAtSolutionLevel, Boolean isLoadedFromFile, VisualStudioVersion vsVersion, ComponentUniqueName componentName, TaskSettings componentTaskSettings,
eption, String targetFramework)

:|
Back to top
Remco
#3 Posted : Tuesday, March 21, 2017 11:23:59 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 960 times
Was thanked: 1290 time(s) in 1196 post(s)
I've yet to test whether this is possible without Visual Studio. Most likely there is a maze of things you'll need to have installed.

Are you also able to build the solution on this machine using MSBuild?
Back to top
GreenMoose
#4 Posted : Wednesday, March 22, 2017 9:25:56 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 6/17/2012(UTC)
Posts: 507

Thanks: 145 times
Was thanked: 66 time(s) in 64 post(s)
Remco;10077 wrote:
I've yet to test whether this is possible without Visual Studio. Most likely there is a maze of things you'll need to have installed.

Are you also able to build the solution on this machine using MSBuild?


Hrm didn't actually try with MSBuild and when I did it complained about missing sdks for MsBuild for some reason, but patching via
Quote:
mklink /J "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\Sdks" "C:\Program Files\dotnet\sdk\1.0.1\Sdks"

both MsBuild and NCrunch work :)
Back to top
1 user thanked GreenMoose for this useful post.
Remco on 3/22/2017(UTC)
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.033 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download