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

Notification

Icon
Error
.NET Core 2.0.1, ASP.NET Core 2.0.1 on a Grid Node Server
Options
Previous Topic Next Topic
Der-Albert.com
#1 Posted : Thursday, November 16, 2017 4:20:15 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/17/2011(UTC)
Posts: 175

Thanks: 8 times
Was thanked: 38 time(s) in 35 post(s)
Hi,

i had a more or less running NCrunch Grid Node with 3.12.04 (on Node and Client) building and testing an ASP.NET Core 2.0 projects.

Now up upgraded to 2.0.1, nothing works anymore it even does not build.

Repro.

Optional Update to VS 17 15.4.4 (because of the Templates)

File New Project .NET Core/ASP.NET App/MVC.

If your Project File does not the 2.0.3 Version, simply upgrade vom 2.0.0 to 2.0.3, upgrade Tools to 2.0.1

Code:
<Project Sdk="Microsoft.NET.Sdk.Web">

  <PropertyGroup>
    <TargetFramework>netcoreapp2.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.All" Version="2.0.3" />
  </ItemGroup>

  <ItemGroup>
    <DotNetCliToolReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Tools" Version="2.0.1" />
  </ItemGroup>

</Project>


No see following build errors

Quote:
NCrunch: This project was built on server 'DELL-E-6420'
Controllers\HomeController.cs (6, 28): The type or namespace name 'Mvc' does not exist in the namespace 'Microsoft.AspNetCore' (are you missing an assembly reference?)
Startup.cs (5, 28): The type or namespace name 'Builder' does not exist in the namespace 'Microsoft.AspNetCore' (are you missing an assembly reference?)
Controllers\HomeController.cs (11, 35): The type or namespace name 'Controller' could not be found (are you missing a using directive or an assembly reference?)
Controllers\HomeController.cs (13, 16): The type or namespace name 'IActionResult' could not be found (are you missing a using directive or an assembly reference?)
Program.cs (20, 23): The type or namespace name 'IWebHost' could not be found (are you missing a using directive or an assembly reference?)
Controllers\HomeController.cs (18, 16): The type or namespace name 'IActionResult' could not be found (are you missing a using directive or an assembly reference?)
Controllers\HomeController.cs (25, 16): The type or namespace name 'IActionResult' could not be found (are you missing a using directive or an assembly reference?)
Controllers\HomeController.cs (32, 16): The type or namespace name 'IActionResult' could not be found (are you missing a using directive or an assembly reference?)
Startup.cs (28, 31): The type or namespace name 'IApplicationBuilder' could not be found (are you missing a using directive or an assembly reference?)
Startup.cs (28, 56): The type or namespace name 'IHostingEnvironment' could not be found (are you missing a using directive or an assembly reference?)



Locally it builds file, on the grid node it fails.

I even updated all VS Version to 15.4.4 (locally and grid node), does not help.

Going back to 2.0.0, it works.

dotnet build with AspNetCore.All 2.0.3, on the grid node server works.

Best Regards

Albert
Back to top
BLOG
Der-Albert.com
#2 Posted : Thursday, November 16, 2017 4:26:51 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/17/2011(UTC)
Posts: 175

Thanks: 8 times
Was thanked: 38 time(s) in 35 post(s)
Now i'm doing a complete reset of the Grid Node Machine. Installing Visual Studio, .NET Core and Grid Node from scratch
Back to top
BLOG
Der-Albert.com
#3 Posted : Thursday, November 16, 2017 5:56:59 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/17/2011(UTC)
Posts: 175

Thanks: 8 times
Was thanked: 38 time(s) in 35 post(s)
It's getting worse.

I reset the Grid Node PC, INstalled .NET SDK, NCrunch, Visual Studio

Quote:

NCrunch: This project was built on server 'DELL-E-6420'
NCrunch was unable to parse this project file because of an unexpected error: Microsoft.Build.Exceptions.InvalidProjectFileException: The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="(- BROKEN LINK -)" to the <Project> element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.
at Microsoft.Build.Shared.ProjectErrorUtilities.ThrowInvalidProject(String errorSubCategoryResourceName, IElementLocation elementLocation, String resourceName, Object[] args)
at Microsoft.Build.Construction.ProjectParser.Parse()
at Microsoft.Build.Construction.ProjectParser.Parse(XmlDocumentWithLocation document, ProjectRootElement projectRootElement)
at Microsoft.Build.Construction.ProjectRootElement..ctor(XmlReader xmlReader, ProjectRootElementCache projectRootElementCache, Boolean isExplicitlyLoaded)
at Microsoft.Build.Construction.ProjectRootElement.Create(XmlReader xmlReader, ProjectCollection projectCollection)
at Microsoft.Build.Evaluation.Project..ctor(XmlReader xmlReader, IDictionary`2 globalProperties, String toolsVersion, String subToolsetVersion, ProjectCollection projectCollection, ProjectLoadSettings loadSettings)
at nCrunch.VSIntegration2010.MSBuildIntegration.BuildableProject2010.Initialise(BuildXml buildXml, FilePath projectFilePath, IDictionary`2 globalProperties)
at nCrunch.Compiler.RemoteBuildRunner.(ComponentBuildParameters )
at nCrunch.Compiler.RemoteBuildRunner..()
at nCrunch.Common.PerformanceTracking.PerfTracker.TrackActivity(String name, Action activity)
at nCrunch.Compiler.RemoteBuildRunner.(ComponentBuildParameters )


WARNING - NCrunch: This project has been built with MSBuild v4.0 because MSBuild v15.0 was not found on this server. Some build tasks may fail when not executed using the correct version of MSBuild.

NCrunch: The following files were used when building this project locally but do not seem to exist on the remote grid node responsible for building this project:
C:\Program Files (x86)\Microsoft SDKs\TypeScript\versions\02.03.05.00.props

Often this can be caused by configuration differences between your client machine and the grid node, in which case the installed SDK directories may be different between machines. If you are experiencing consistent problems when building this project on the grid node, the missing files listed above are worth investigating as they may highlight SDKs required on the grid node that have not yet been installed. Please note that this is not necessarily an error case as projects very often build successfully on grid nodes with only a subset of the client machine's installed SDKs.




The Main Problems seems thet MSBuild v4.0 is instead of MSBuild 15 was used.

Best Regards

Albert
Back to top
BLOG
Remco
#4 Posted : Thursday, November 16, 2017 10:55:58 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 931 times
Was thanked: 1257 time(s) in 1170 post(s)
Hi Albert, thanks for sharing these problems.

The 'DotNetCliToolReference' tag is a new one to me. Every time I see something like this, my inners contract in fear as it's usually evidence that MS have yet again rewired the assembly referencing system in .NET Core. NCrunch hasn't seen any organised testing around the logic attached to this reference type, so it may be a source of problems until we can find time to fix it. It's interesting that the project still builds for you locally but not on the grid node. This suggests that the problem may be in the logic used to synchronise the client and node. It may well be possible to build this on the grid node if all the packages are fully restored on this node under the expected location (try pre-building the solution on the node manually and making sure you run the node under a local user profile).

Failing that, v3.12.0.13 is further along than v3.12.0.4, as it includes a few grid synchronisation fixes. It may be worth a shot:

http://downloads.ncrunch.net/NCrunch_Console_3.12.0.13.msi
http://downloads.ncrunch.net/NCrunch_Console_3.12.0.13.zip
http://downloads.ncrunch.net/NCrunch_GridNodeServer_3.12.0.13.msi
http://downloads.ncrunch.net/NCrunch_GridNodeServer_3.12.0.13.zip
http://downloads.ncrunch.net/NCrunch_LicenseServer_3.12.0.13.zip
http://downloads.ncrunch.net/NCrunch_VS2008_3.12.0.13.msi
http://downloads.ncrunch.net/NCrunch_VS2010_3.12.0.13.msi
http://downloads.ncrunch.net/NCrunch_VS2010_3.12.0.13.zip
http://downloads.ncrunch.net/NCrunch_VS2012_3.12.0.13.msi
http://downloads.ncrunch.net/NCrunch_VS2012_3.12.0.13.zip
http://downloads.ncrunch.net/NCrunch_VS2013_3.12.0.13.msi
http://downloads.ncrunch.net/NCrunch_VS2013_3.12.0.13.zip
http://downloads.ncrunch.net/NCrunch_VS2015_3.12.0.13.msi
http://downloads.ncrunch.net/NCrunch_VS2015_3.12.0.13.zip
http://downloads.ncrunch.net/NCrunch_VS2017_3.12.0.13.msi
http://downloads.ncrunch.net/NCrunch_VS2017_3.12.0.13.zip

The problem you're experiencing with the wrong version of MSBuild being used is likely to be a problem with the install state on the grid node that's newly introduced after the wipe. When the grid node initialises, it creates an internal registry of versions of MSBuild/VS that are locally installed and it will always try to use the version matching the one requested by the client. Under VS2017, it primarily uses the VS COM API, since VS2017 installations aren't referenced as singletons in the registry and can't really be found any other way. I've had reports that this API doesn't seem to always return a result when it should (unable to recreate myself), so there are also fallbacks in place to try and find other ways to discover the installation. If you set the NCrunchVSInstallPath.VS2017 environment variable to the installation path of your VS instance, NCrunch should be able to find it without needing the API. Make sure this references the directory two levels above the one containing devenv.exe.
Back to top
Der-Albert.com
#5 Posted : Friday, November 17, 2017 11:36:59 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/17/2011(UTC)
Posts: 175

Thanks: 8 times
Was thanked: 38 time(s) in 35 post(s)
I forgot to mention, that i installed 3.12.0.13 a part of the reset.

But i've installed NCrunch before VS. Would be nice to rerun the init in case of adding or switching VS Versions.

I'd set the Env Variable, and it builds not with the same error as before. So, the reset was only a timesink, on the other hand. the system is now clean and has plenty of space.

On the "Old" Node i copied a bunch of stuff to several places so that the .NET Core 2.0 Build worked (you may remember). I would like to avoid this now.

Changing the AspNetCore.All depenency Version to 2.0.0 will make the project build fine, but this is not an option in the real projects because of the security fixes.

The DotNetCliToolReference is part of the Sdk Style Project since Day 1.

Quote:

NCrunch: This project was built on server 'DELL-E-6420'
ActiveCssControllerTagHelper.cs (3, 28): The type or namespace name 'Mvc' does not exist in the namespace 'Microsoft.AspNetCore' (are you missing an assembly reference?)
ActiveCssControllerTagHelper.cs (4, 28): The type or namespace name 'Mvc' does not exist in the namespace 'Microsoft.AspNetCore' (are you missing an assembly reference?)
ActiveCssControllerTagHelper.cs (5, 28): The type or namespace name 'Razor' does not exist in the namespace 'Microsoft.AspNetCore' (are you missing an assembly reference?)
ActiveCssPageTagHelper.cs (3, 28): The type or namespace name 'Mvc' does not exist in the namespace 'Microsoft.AspNetCore' (are you missing an assembly reference?)
ActiveCssPageTagHelper.cs (4, 28): The type or namespace name 'Razor' does not exist in the namespace 'Microsoft.AspNetCore' (are you missing an assembly reference?)
AuthorizeTagHelper.cs (3, 28): The type or namespace name 'Authorization' does not exist in the namespace 'Microsoft.AspNetCore' (are you missing an assembly reference?)
AuthorizeTagHelper.cs (4, 28): The type or namespace name 'Http' does not exist in the namespace 'Microsoft.AspNetCore' (are you missing an assembly reference?)
AuthorizeTagHelper.cs (5, 28): The type or namespace name 'Razor' does not exist in the namespace 'Microsoft.AspNetCore' (are you missing an assembly reference?)
BootstrapTagHelper.cs (5, 28): The type or namespace name 'Razor' does not exist in the namespace 'Microsoft.AspNetCore' (are you missing an assembly reference?)
TagHelperComponents\VersionTagHelperComponent.cs (5, 28): The type or namespace name 'Razor' does not exist in the namespace 'Microsoft.AspNetCore' (are you missing an assembly reference?)
TagHelperExtensions.cs (2, 28): The type or namespace name 'Razor' does not exist in the namespace 'Microsoft.AspNetCore' (are you missing an assembly reference?)
TagHelperOutputExtensions.cs (1, 28): The type or namespace name 'Razor' does not exist in the namespace 'Microsoft.AspNetCore' (are you missing an assembly reference?)
AuthorizeTagHelper.cs (10, 39): The type or namespace name 'TagHelper' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (20, 49): The type or namespace name 'TagHelper' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssPageTagHelper.cs (12, 43): The type or namespace name 'TagHelper' could not be found (are you missing a using directive or an assembly reference?)
BootstrapTagHelper.cs (12, 39): The type or namespace name 'TagHelper' could not be found (are you missing a using directive or an assembly reference?)
AuthorizeTagHelper.cs (9, 6): The type or namespace name 'HtmlTargetElementAttribute' could not be found (are you missing a using directive or an assembly reference?)
BootstrapTagHelper.cs (10, 6): The type or namespace name 'HtmlTargetElementAttribute' could not be found (are you missing a using directive or an assembly reference?)
AuthorizeTagHelper.cs (9, 6): The type or namespace name 'HtmlTargetElement' could not be found (are you missing a using directive or an assembly reference?)
BootstrapTagHelper.cs (10, 6): The type or namespace name 'HtmlTargetElement' could not be found (are you missing a using directive or an assembly reference?)
AuthorizeTagHelper.cs (9, 24): The type or namespace name 'Attributes' could not be found (are you missing a using directive or an assembly reference?)
BootstrapTagHelper.cs (10, 24): The type or namespace name 'Attributes' could not be found (are you missing a using directive or an assembly reference?)
TagHelperComponents\VersionTagHelperComponent.cs (9, 46): The type or namespace name 'TagHelperComponent' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssPageTagHelper.cs (9, 6): The type or namespace name 'HtmlTargetElementAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssPageTagHelper.cs (9, 6): The type or namespace name 'HtmlTargetElement' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssPageTagHelper.cs (10, 6): The type or namespace name 'HtmlTargetElementAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssPageTagHelper.cs (10, 6): The type or namespace name 'HtmlTargetElement' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssPageTagHelper.cs (11, 6): The type or namespace name 'HtmlTargetElementAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssPageTagHelper.cs (11, 6): The type or namespace name 'HtmlTargetElement' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssPageTagHelper.cs (9, 24): The type or namespace name 'Attributes' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssPageTagHelper.cs (10, 24): The type or namespace name 'Attributes' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssPageTagHelper.cs (11, 24): The type or namespace name 'Attributes' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssPageTagHelper.cs (35, 43): The type or namespace name 'TagHelperContext' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssPageTagHelper.cs (35, 69): The type or namespace name 'TagHelperOutput' could not be found (are you missing a using directive or an assembly reference?)
BootstrapTagHelper.cs (19, 49): The type or namespace name 'TagHelperContext' could not be found (are you missing a using directive or an assembly reference?)
AuthorizeTagHelper.cs (25, 49): The type or namespace name 'TagHelperContext' could not be found (are you missing a using directive or an assembly reference?)
BootstrapTagHelper.cs (19, 75): The type or namespace name 'TagHelperOutput' could not be found (are you missing a using directive or an assembly reference?)
AuthorizeTagHelper.cs (25, 75): The type or namespace name 'TagHelperOutput' could not be found (are you missing a using directive or an assembly reference?)
AuthorizeTagHelper.cs (25, 36): 'AuthorizeTagHelper.ProcessAsync(TagHelperContext, TagHelperOutput)': no suitable method found to override
ActiveCssPageTagHelper.cs (44, 37): The type or namespace name 'TagHelperOutput' could not be found (are you missing a using directive or an assembly reference?)
TagHelperComponents\VersionTagHelperComponent.cs (53, 38): The type or namespace name 'TagHelperContext' could not be found (are you missing a using directive or an assembly reference?)
TagHelperComponents\VersionTagHelperComponent.cs (53, 64): The type or namespace name 'TagHelperOutput' could not be found (are you missing a using directive or an assembly reference?)
TagHelperComponents\VersionTagHelperComponent.cs (53, 30): 'VersionTagHelperComponent.Process(TagHelperContext, TagHelperOutput)': no suitable method found to override
ActiveCssPageTagHelper.cs (35, 30): 'ActiveCssPageTagHelper.ProcessAsync(TagHelperContext, TagHelperOutput)': no suitable method found to override
BootstrapTagHelper.cs (28, 44): The type or namespace name 'TagHelperContext' could not be found (are you missing a using directive or an assembly reference?)
BootstrapTagHelper.cs (28, 70): The type or namespace name 'TagHelperOutput' could not be found (are you missing a using directive or an assembly reference?)
AuthorizeTagHelper.cs (16, 35): The type or namespace name 'IAuthorizationService' could not be found (are you missing a using directive or an assembly reference?)
AuthorizeTagHelper.cs (16, 79): The type or namespace name 'IHttpContextAccessor' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssPageTagHelper.cs (17, 39): The type or namespace name 'IActionContextAccessor' could not be found (are you missing a using directive or an assembly reference?)
AuthorizeTagHelper.cs (12, 26): The type or namespace name 'IAuthorizationService' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssPageTagHelper.cs (14, 26): The type or namespace name 'IActionContextAccessor' could not be found (are you missing a using directive or an assembly reference?)
AuthorizeTagHelper.cs (13, 26): The type or namespace name 'IHttpContextAccessor' could not be found (are you missing a using directive or an assembly reference?)
BootstrapTagHelper.cs (37, 63): The type or namespace name 'TagHelperContext' could not be found (are you missing a using directive or an assembly reference?)
BootstrapTagHelper.cs (37, 89): The type or namespace name 'TagHelperOutput' could not be found (are you missing a using directive or an assembly reference?)
BootstrapTagHelper.cs (19, 36): 'BootstrapTagHelper.ProcessAsync(TagHelperContext, TagHelperOutput)': no suitable method found to override
ActiveCssPageTagHelper.cs (27, 10): The type or namespace name 'HtmlAttributeNameAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssPageTagHelper.cs (27, 10): The type or namespace name 'HtmlAttributeName' could not be found (are you missing a using directive or an assembly reference?)
AuthorizeTagHelper.cs (22, 10): The type or namespace name 'HtmlAttributeNameAttribute' could not be found (are you missing a using directive or an assembly reference?)
AuthorizeTagHelper.cs (22, 10): The type or namespace name 'HtmlAttributeName' could not be found (are you missing a using directive or an assembly reference?)
TagHelperOutputExtensions.cs (7, 51): The type or namespace name 'TagHelperOutput' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssPageTagHelper.cs (30, 10): The type or namespace name 'HtmlAttributeNameAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssPageTagHelper.cs (30, 10): The type or namespace name 'HtmlAttributeName' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssPageTagHelper.cs (32, 10): The type or namespace name 'HtmlAttributeNameAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssPageTagHelper.cs (32, 10): The type or namespace name 'HtmlAttributeName' could not be found (are you missing a using directive or an assembly reference?)
BootstrapTagHelper.cs (16, 10): The type or namespace name 'HtmlAttributeNameAttribute' could not be found (are you missing a using directive or an assembly reference?)
BootstrapTagHelper.cs (16, 10): The type or namespace name 'HtmlAttributeName' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (10, 6): The type or namespace name 'HtmlTargetElementAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (10, 6): The type or namespace name 'HtmlTargetElement' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (11, 6): The type or namespace name 'HtmlTargetElementAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (11, 6): The type or namespace name 'HtmlTargetElement' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (12, 6): The type or namespace name 'HtmlTargetElementAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (12, 6): The type or namespace name 'HtmlTargetElement' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (13, 6): The type or namespace name 'HtmlTargetElementAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (13, 6): The type or namespace name 'HtmlTargetElement' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (14, 6): The type or namespace name 'HtmlTargetElementAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (14, 6): The type or namespace name 'HtmlTargetElement' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (15, 6): The type or namespace name 'HtmlTargetElementAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (15, 6): The type or namespace name 'HtmlTargetElement' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (16, 6): The type or namespace name 'HtmlTargetElementAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (16, 6): The type or namespace name 'HtmlTargetElement' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (17, 6): The type or namespace name 'HtmlTargetElementAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (17, 6): The type or namespace name 'HtmlTargetElement' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (18, 6): The type or namespace name 'HtmlTargetElementAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (18, 6): The type or namespace name 'HtmlTargetElement' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (19, 6): The type or namespace name 'HtmlTargetElementAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (19, 6): The type or namespace name 'HtmlTargetElement' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (10, 24): The type or namespace name 'Attributes' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (11, 24): The type or namespace name 'Attributes' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (12, 24): The type or namespace name 'Attributes' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (13, 24): The type or namespace name 'Attributes' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (14, 24): The type or namespace name 'Attributes' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (15, 24): The type or namespace name 'Attributes' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (16, 24): The type or namespace name 'Attributes' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (17, 24): The type or namespace name 'Attributes' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (18, 24): The type or namespace name 'Attributes' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (19, 24): The type or namespace name 'Attributes' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (77, 43): The type or namespace name 'TagHelperContext' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (77, 69): The type or namespace name 'TagHelperOutput' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (94, 37): The type or namespace name 'TagHelperOutput' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (153, 64): The type or namespace name 'ActionDescriptor' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (77, 30): 'ActiveCssControllerTagHelper.ProcessAsync(TagHelperContext, TagHelperOutput)': no suitable method found to override
ActiveCssControllerTagHelper.cs (37, 45): The type or namespace name 'IActionContextAccessor' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (34, 26): The type or namespace name 'IActionContextAccessor' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (43, 10): The type or namespace name 'HtmlAttributeNameAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (43, 10): The type or namespace name 'HtmlAttributeName' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (46, 10): The type or namespace name 'HtmlAttributeNameAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (46, 10): The type or namespace name 'HtmlAttributeName' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (49, 10): The type or namespace name 'HtmlAttributeNameAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (49, 10): The type or namespace name 'HtmlAttributeName' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (53, 10): The type or namespace name 'HtmlAttributeNameAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (53, 10): The type or namespace name 'HtmlAttributeName' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (57, 10): The type or namespace name 'HtmlAttributeNameAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (57, 10): The type or namespace name 'HtmlAttributeName' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (60, 10): The type or namespace name 'HtmlAttributeNameAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (60, 10): The type or namespace name 'HtmlAttributeName' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (63, 10): The type or namespace name 'HtmlAttributeNameAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (63, 10): The type or namespace name 'HtmlAttributeName' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (67, 10): The type or namespace name 'HtmlAttributeNameAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (67, 10): The type or namespace name 'HtmlAttributeName' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (70, 10): The type or namespace name 'HtmlAttributeNameAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (70, 10): The type or namespace name 'HtmlAttributeName' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (74, 10): The type or namespace name 'HtmlAttributeNameAttribute' could not be found (are you missing a using directive or an assembly reference?)
ActiveCssControllerTagHelper.cs (74, 10): The type or namespace name 'HtmlAttributeName' could not be found (are you missing a using directive or an assembly reference?)
Back to top
BLOG
GreenMoose
#6 Posted : Friday, November 17, 2017 2:02:29 PM(UTC)
Rank: Advanced Member

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

Thanks: 142 times
Was thanked: 66 time(s) in 64 post(s)
In case you haven't tried it already:
1) Ensure NCrunch grid node service is not running under system account, use a "normal" account instead (also preferable for security reasons).
2) Run nuget restore / dotnet restore, before building with NCrunch. First time this will perform a large list of nuget caching for the current user. You can do this manually on CI server by simply running a nuget restore on the solution, running under the same user as the grid node service is using.

HTH
Back to top
Der-Albert.com
#7 Posted : Friday, November 17, 2017 2:08:27 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/17/2011(UTC)
Posts: 175

Thanks: 8 times
Was thanked: 38 time(s) in 35 post(s)
Yes, i know the System Account Issue.
dotnet build for a ASP.NET Core 2.0.1 project (dotnet new mvc, dotnet run) works on the machine.
Back to top
BLOG
Remco
#8 Posted : Monday, November 20, 2017 5:21:45 AM(UTC)
Rank: NCrunch Developer

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

Thanks: 931 times
Was thanked: 1257 time(s) in 1170 post(s)
Back to top
Der-Albert.com
#9 Posted : Monday, November 20, 2017 9:38:55 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/17/2011(UTC)
Posts: 175

Thanks: 8 times
Was thanked: 38 time(s) in 35 post(s)
Thumbs up. It is now working, without changing anything (besides the update) on the Grid Node Server.
Back to top
BLOG
Remco
#10 Posted : Monday, November 20, 2017 10:10:04 AM(UTC)
Rank: NCrunch Developer

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

Thanks: 931 times
Was thanked: 1257 time(s) in 1170 post(s)
Der-Albert.com;11517 wrote:
Thumbs up. It is now working, without changing anything (besides the update) on the Grid Node Server.


Excellent! Thanks for confirming :)
Back to top
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.192 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download