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

Notification

Icon
Error

Ncrunch Tool Issue with .net Core 2.0
sunil
#1 Posted : Wednesday, August 09, 2017 10:44:17 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 8/9/2017(UTC)
Posts: 6

I am successfully able to build and run tests in Vs2017 Preview. I am using Ncrunch 3.10.0.20. But when I try to use the Ncrunch Tool I get the following error. Seems like it is trying to use the wrong msbuild version. I have tried passing in /vs 2017 but get the same error.


NCrunch Console Tool v3.10.0.20
Copyright c 2010-2017 Remco Software Ltd
Usage of this tool is permitted only under the terms described in License.rtf



This product is licensed to

[17:26:07.5682-?-1] Initialising UI Services
[17:26:07.6153-?-1] NCrunch Services Initialised
[17:26:07.6533-?-1] Publishing Event: [EngineModeSwitchedInUIEvent:Run all tests automatically [Global]]
[17:26:07.6553-?-1] Event [EngineModeSwitchedInUIEvent:Run all tests automatically [Global]] is being published on thread CoreThread to subscriber: ClientSettingsBlock.
[17:26:07.6612-?-1] Publishing Event: [EngineModesChangedEvent]
[17:26:07.6632-Core-4] Event [EngineModeSwitchedInUIEvent:Run all tests automatically [Global]] is being processed on Core thread with subscriber: ClientSettingsBlock.
[17:26:08.0372-Core-7] Loading NCrunch modules
[17:26:08.0423-Core-7] Loading module: C:\dev\NCrunchConsoleTool3.10\Modules\Gallio\nCrunch.Module.Gallio.crunchmodule
[17:26:08.0503-Core-7] Loading module: C:\dev\NCrunchConsoleTool3.10\Modules\MSpec\nCrunch.Module.MSpec.crunchmodule
[17:26:08.0533-Core-7] Loading module: C:\dev\NCrunchConsoleTool3.10\Modules\MSTest\nCrunch.Module.MSTest.crunchmodule
[17:26:08.0584-Core-7] Loading module: C:\dev\NCrunchConsoleTool3.10\Modules\NUnit\nCrunch.Module.NUnit.crunchmodule
[17:26:08.0623-Core-7] Loading module: C:\dev\NCrunchConsoleTool3.10\Modules\NUnit3\nCrunch.Module.NUnit3.crunchmodule
[17:26:08.0693-Core-7] Loading module: C:\dev\NCrunchConsoleTool3.10\Modules\XUnit2\nCrunch.Module.XUnit2.crunchmodule
[17:26:09.5753-Core-7] Framework description manager has loaded data for 6 test frameworks
[17:26:09.7363-InitialisationQueueTask-15] Auto restoring NuGet packages for 'c:\dev\checkbee\src\DMI.CheckBee\DMI.CheckBee.csproj'
[17:26:11.9153-InitialisationQueueTask-15] Loading project: c:\dev\checkbee\src\DMI.CheckBee\DMI.CheckBee.csproj
[17:26:19.9813-InitialisationQueueTask-13] Auto restoring NuGet packages for 'c:\dev\checkbee\src\DMI.CheckBee.Tests\DMI.CheckBee.Tests.csproj'
[17:26:22.0683-InitialisationQueueTask-13] Loading project: c:\dev\checkbee\src\DMI.CheckBee.Tests\DMI.CheckBee.Tests.csproj
[17:26:23.8613-InitialisationQueueTask-14] Auto restoring NuGet packages for 'c:\dev\checkbee\src\DMI.CheckBee.Data.Tests\DMI.CheckBee.Data.Tests.csproj'
[17:26:24.9692-InitialisationQueueTask-14] Loading project: c:\dev\checkbee\src\DMI.CheckBee.Data.Tests\DMI.CheckBee.Data.Tests.csproj
[17:26:26.1967-InitialisationQueueTask-12] Auto restoring NuGet packages for 'c:\dev\checkbee\src\DMI.CheckBee.Data\DMI.CheckBee.Data.csproj'
[17:26:27.1027-InitialisationQueueTask-12] Loading project: c:\dev\checkbee\src\DMI.CheckBee.Data\DMI.CheckBee.Data.csproj
[17:26:33.2227-InitialisationQueueTask-15] Auto restoring NuGet packages for 'c:\dev\checkbee\src\DMI.CheckBee.Core\DMI.CheckBee.Core.csproj'
[17:26:34.0877-InitialisationQueueTask-15] Loading project: c:\dev\checkbee\src\DMI.CheckBee.Core\DMI.CheckBee.Core.csproj
[17:26:34.5707-InitialisationQueueTask-12] Auto restoring NuGet packages for 'c:\dev\checkbee\src\DMI.CheckBee.Business\DMI.CheckBee.Business.csproj'
[17:26:35.7487-InitialisationQueueTask-12] Loading project: c:\dev\checkbee\src\DMI.CheckBee.Business\DMI.CheckBee.Business.csproj
[17:26:36.6987-InitialisationQueueTask-13] Auto restoring NuGet packages for 'c:\dev\checkbee\src\DMI.Messages\DMI.Messages.csproj'
[17:26:37.5246-InitialisationQueueTask-13] Loading project: c:\dev\checkbee\src\DMI.Messages\DMI.Messages.csproj
[17:26:37.9256-InitialisationQueueTask-9] Auto restoring NuGet packages for 'c:\dev\checkbee\src\DMI.CheckBee.Messaging\DMI.CheckBee.Messaging.csproj'
[17:26:38.9396-InitialisationQueueTask-9] Loading project: c:\dev\checkbee\src\DMI.CheckBee.Messaging\DMI.CheckBee.Messaging.csproj
[17:26:39.6316-Core-7] All projects have been loaded
[17:26:39.7836-Core-7] Queuing 6 tests for passive execution
[17:26:39.8166-Core-7] Queuing 129 tests for passive execution
[17:26:39.8906-LocalBuildTask-14] Building new workspace C:\Users\sbhujle\AppData\Local\NCrunch\15128\1 for component DMI.CheckBee.Core in context of grid client (local)
[17:26:39.8956-Core-7] Queuing 129 tests for passive execution
[17:26:40.0026-LocalBuildTask-14] Now building DMI.CheckBee.Core
[17:26:40.0986-Core-16] Queuing 129 tests for passive execution
[17:26:40.0986-Core-16] Queuing 6 tests for passive execution
[17:26:44.5634-LocalBuildTask-14] Build was successful for C:\Users\sbhujle\AppData\Local\NCrunch\15128\1\DMI.CheckBee.Core\bin\Debug\netcoreapp2.0\DMI.CheckBee.Core.dll
[17:26:44.6053-LocalBuildTask-25] Building new workspace C:\Users\sbhujle\AppData\Local\NCrunch\15128\2 for component DMI.CheckBee.Data in context of grid client (local)
[17:26:44.7443-LocalBuildTask-25] Now building DMI.CheckBee.Data
[17:26:46.2239-LocalBuildTask-25] Build was successful for C:\Users\sbhujle\AppData\Local\NCrunch\15128\2\DMI.CheckBee.Data\bin\Debug\netcoreapp2.0\DMI.CheckBee.Data.dll
[17:26:46.2319-LocalBuildTask-14] Building new workspace C:\Users\sbhujle\AppData\Local\NCrunch\15128\3 for component DMI.CheckBee.Data.Tests in context of grid client (local)
[17:26:46.267-LocalBuildTask-14] Now building DMI.CheckBee.Data.Tests
[17:26:54.1303-LocalBuildTask-14] Build was successful for C:\Users\sbhujle\AppData\Local\NCrunch\15128\3\DMI.CheckBee.Data.Tests\bin\Debug\netcoreapp2.0\DMI.CheckBee.Data.Tests.dll
[17:26:54.1383-LocalBuildTask-10] Building new workspace C:\Users\sbhujle\AppData\Local\NCrunch\15128\4 for component DMI.CheckBee.Business in context of grid client (local)
[17:26:54.2569-LocalBuildTask-10] Now building DMI.CheckBee.Business
[17:27:01.8645-LocalBuildTask-10] Build was successful for C:\Users\sbhujle\AppData\Local\NCrunch\15128\4\DMI.CheckBee.Business\bin\Debug\netcoreapp2.0\DMI.CheckBee.Business.dll
[17:27:01.8705-LocalBuildTask-22] Building new workspace C:\Users\sbhujle\AppData\Local\NCrunch\15128\5 for component DMI.Messages in context of grid client (local)
[17:27:01.8895-LocalBuildTask-22] Now building DMI.Messages
[17:27:02.8982-LocalBuildTask-22] Build was successful for C:\Users\sbhujle\AppData\Local\NCrunch\15128\5\DMI.Messages\bin\Debug\netstandard1.6\DMI.Messages.dll
[17:27:02.9062-LocalBuildTask-11] Building new workspace C:\Users\sbhujle\AppData\Local\NCrunch\15128\6 for component DMI.CheckBee.Messaging in context of grid client (local)
[17:27:03.0107-LocalBuildTask-11] Now building DMI.CheckBee.Messaging
[17:27:04.0407-LocalBuildTask-11] Build was successful for C:\Users\sbhujle\AppData\Local\NCrunch\15128\6\DMI.CheckBee.Messaging\bin\Debug\netcoreapp2.0\DMI.CheckBee.Messaging.dll
[17:27:04.0447-LocalBuildTask-20] Building new workspace C:\Users\sbhujle\AppData\Local\NCrunch\15128\7 for component DMI.CheckBee in context of grid client (local)
[17:27:04.2226-LocalBuildTask-20] Now building DMI.CheckBee
[17:27:05.6666-LocalBuildTask-20] ERROR (Build): DMI.CheckBee: C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\TypeScript\Microsoft.TypeScript.targets (87): The "TypeScript.Tasks.VsTsc" task could not be loaded from the assembly C:\Program Files (x86)\Microsoft Visual Studio\Preview\Professional\MSBuild\Microsoft\VisualStudio\v11.0\TypeScript\TypeScript.tasks.dll. Could not load file or assembly 'file:///C:\Program Files (x86)\Microsoft Visual Studio\Preview\Professional\MSBuild\Microsoft\VisualStudio\v11.0\TypeScript\TypeScript.tasks.dll' or one of its dependencies. The system cannot find the file specified. Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.

[17:27:06.2856-LocalAnalysisTask-11] Calling into task runner to analyse target assembly: C:\Users\sbhujle\AppData\Local\NCrunch\15128\3\DMI.CheckBee.Data.Tests\bin\Debug\netcoreapp2.0\DMI.CheckBee.Data.Tests.dll
[17:27:06.5007-LocalTestExecutionTask-12] Calling into task runner to run 5 tests:
DMI.CheckBee.Data.Tests.Repositories.TransactionRepositoryTests+GetTransactionAsyncMethod.Should_fetch_the_transaction_when_the_cardholder_program_is_in_the_specified_program_ids_Async
DMI.CheckBee.Data.Tests.Repositories.TransactionRepositoryTests+GetTransactionAsyncMethod.Should_return_null_when_no_program_ids_are_specified_Async
DMI.CheckBee.Data.Tests.Repositories.TransactionRepositoryTests+GetTransactionAsyncMethod.Should_return_null_when_specified_program_ids_is_null_Async
DMI.CheckBee.Data.Tests.Repositories.TransactionRepositoryTests+GetTransactionAsyncMethod.Should_return_null_when_the_cardholder_program_is_not_in_the_specified_program_ids_Async
DMI.CheckBee.Data.Tests.Repositories.TransactionRepositoryTests+GetTransactionAsyncMethod.Should_return_null_when_the_specified_transaction_id_is_not_found_Async
[17:27:07.2966-Core-10] Successfully completed execution of 5 tests on local machine
[17:27:07.3626-LocalTestExecutionTask-23] Calling into task runner to run 1 tests:
DMI.CheckBee.Data.Tests.Authorization.AuthorizationTests.Find_user_permission
[17:27:07.6577-Core-15] Successfully completed execution of 1 tests on local machine
[17:27:09.5402-?-1] Reporting engine execution results
[17:27:09.8552-?-1] Shutting down engine
[17:27:09.9402-Core-37] Cleaning up workspace: C:\Users\sbhujle\AppData\Local\NCrunch\15128\7
[17:27:09.9652-Core-37] Cleaning up workspace: C:\Users\sbhujle\AppData\Local\NCrunch\15128\4
[17:27:09.9892-Core-37] Cleaning up workspace: C:\Users\sbhujle\AppData\Local\NCrunch\15128\5
[17:27:09.9982-Core-37] Cleaning up workspace: C:\Users\sbhujle\AppData\Local\NCrunch\15128\6
[17:27:10.0142-Core-37] Cleaning up workspace: C:\Users\sbhujle\AppData\Local\NCrunch\15128\3
[17:27:10.0302-Core-37] Cleaning up workspace: C:\Users\sbhujle\AppData\Local\NCrunch\15128\1
[17:27:10.0482-Core-37] Cleaning up workspace: C:\Users\sbhujle\AppData\Local\NCrunch\15128\2
[17:27:12.2079-?-1] Returning result: BuildFailure
Remco
#2 Posted : Wednesday, August 09, 2017 11:05:32 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 622 times
Was thanked: 725 time(s) in 690 post(s)
Hi,

Does this solution work using NCrunch on the same system through VS? (i.e. the VS extension)
sunil
#3 Posted : Thursday, August 10, 2017 12:57:36 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 8/9/2017(UTC)
Posts: 6

Yes. The solution works fine running in VS2017. Here are my VS2017 details

Microsoft Visual Studio Professional 2017 Preview (2)
Version 15.3.0 Preview 7.0
VisualStudio.15.Preview/15.3.0-pre.7.0+26730.0
Microsoft .NET Framework
Version 4.6.01586
sunil
#5 Posted : Thursday, August 10, 2017 2:02:37 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 8/9/2017(UTC)
Posts: 6

I have tried this with ncrunch tool 3.9 and 3.8 but get the same error.
Remco
#4 Posted : Thursday, August 10, 2017 4:23:07 AM(UTC)
Rank: NCrunch Developer

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

Thanks: 622 times
Was thanked: 725 time(s) in 690 post(s)
sunil;10947 wrote:
Yes. The solution works fine running in VS2017. Here are my VS2017 details

Microsoft Visual Studio Professional 2017 Preview (2)
Version 15.3.0 Preview 7.0
VisualStudio.15.Preview/15.3.0-pre.7.0+26730.0
Microsoft .NET Framework
Version 4.6.01586


Sorry, I need to confirm your answer here as it's a very important question to help with troubleshooting this. You've shown that the tool fails for this solution when it's run using the NCrunch console tool. Does it work when you run it using NCrunch inside VS? Can the NCrunch engine build these projects when it's hosted inside VS?
sunil
#6 Posted : Thursday, August 10, 2017 12:19:34 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 8/9/2017(UTC)
Posts: 6

Yes the solution builds fine when I run inside of VS. But fails when I run it using the ncrunch tool.
Remco
#7 Posted : Thursday, August 10, 2017 8:25:15 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 622 times
Was thanked: 725 time(s) in 690 post(s)
sunil;10954 wrote:
Yes the solution builds fine when I run inside of VS. But fails when I run it using the ncrunch tool.


But does the solution build when using NCrunch inside VS? If you have NCrunch installed in your VS system, and you enable it, do you see build errors in the NCrunch Tests Window?
sunil
#8 Posted : Friday, August 11, 2017 2:51:11 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 8/9/2017(UTC)
Posts: 6

Yes the solution builds fine jin VS using Ncrunch.


Sorry for being ambiguous about this one.
Remco
#9 Posted : Friday, August 11, 2017 4:53:50 AM(UTC)
Rank: NCrunch Developer

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

Thanks: 622 times
Was thanked: 725 time(s) in 690 post(s)
sunil;10963 wrote:
Yes the solution builds fine jin VS using Ncrunch.


Sorry for being ambiguous about this one.


No problem. Thanks for confirming. I agree this is possibly NCrunch not using the correct version of VS. The only reason I could think of why it might do this is if it were having trouble finding your installed instance of VS2017 preview. Which versions of VS do you have installed on your system, and what are their install paths?
sunil
#10 Posted : Sunday, August 13, 2017 3:23:36 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 8/9/2017(UTC)
Posts: 6

I have the following versions of VS installed

Microsoft Visual Studio Professional 2017 Preview (2)
Version 15.3.0 Preview 7.0
VisualStudio.15.Preview/15.3.0-pre.7.0+26730.0
Microsoft .NET Framework
Version 4.6.01586
Installed Version: Professional
Path is : C:\Program Files (x86)\Microsoft Visual Studio\Preview


Microsoft Visual Studio Professional 2017
Version 15.2 (26430.16) Release
VisualStudio.15.Release/15.2.0+26430.16
Microsoft .NET Framework
Version 4.6.01586
Installed Version: Professional
Path is : C:\Program Files (x86)\Microsoft Visual Studio\2017\

Microsoft Visual Studio Professional 2015
Version 14.0.25424.00 Update 3
Microsoft .NET Framework
Version 4.6.01586
Installed Version: Professional
Path is : C:\Program Files (x86)\Microsoft Visual Studio 14.0

Microsoft Visual Studio Professional 2013
Version 12.0.40629.00 Update 5
Microsoft .NET Framework
Version 4.6.01586
Installed Version: Professional
Path is : C:\Program Files (x86)\Microsoft Visual Studio 12.0\




Remco
#11 Posted : Sunday, August 13, 2017 11:58:14 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 622 times
Was thanked: 725 time(s) in 690 post(s)
The NCrunch console tool doesn't differentiate between VS2017 and VS2017 preview - it considers VS2017 to be VS2017 and is probably just using the first version of VS2017 that it can locate. This might be the reason for the inconsistency.

There is a way to override this. Prior to running the console tool, you can use the "NCrunchVSInstallPath.2017" environment variable to specify the path of the VS instance you want the tool to use. For example:

set NCrunchVSInstallPath.2017=C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise
Users browsing this topic
Guest (3)
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.092 seconds.