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

Notification

Icon
Error
Won't work with Only Visual Studio Build Tools installed on Grid Node
Options
Previous Topic Next Topic
Der-Albert.com
#1 Posted : Wednesday, August 29, 2018 1:22:35 PM(UTC)
Rank: Advanced Member

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

Thanks: 11 times
Was thanked: 55 time(s) in 51 post(s)
Hi,

i decided to remove Visual Studio UI from the Grid Node Server and only used to Visual Studio Build Tools (easier to update, much less in size und download), because also the Docs are
stating that a Grid Node Setup should be more or less the same as a build server.

But this does not work. I tried repairing the NCrunch installation, uninstalling it and install it again. Nothing helps, NCrunch does not find MSBuild 15.0

You can find the Build Tools under https://visualstudio.microsoft.com/downloads/ ->
Tools for Visual Studio 2017 -> Build Tools for Visual Studio 2017

Direkt Link: https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=BuildTools&rel=15


Best Regards

Albert

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 visual studio\2017\professional\MSBuild\15.0\Microsoft.Common.props
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\15.0\Imports\Microsoft.Common.props\ImportBefore\Microsoft.NuGet.ImportBefore.props
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\Microsoft\NuGet\15.0\Microsoft.NuGet.props
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\Microsoft\VisualStudio\v15.0\TypeScript\Microsoft.TypeScript.Default.props
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\15.0\Bin\Microsoft.CSharp.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\15.0\Bin\Microsoft.CSharp.CurrentVersion.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\15.0\Bin\Roslyn\Microsoft.CSharp.Core.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\15.0\Bin\Roslyn\Microsoft.Managed.Core.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\Microsoft\VisualStudio\Managed\Microsoft.CSharp.DesignTime.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\Microsoft\VisualStudio\Managed\Microsoft.Managed.DesignTime.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\15.0\Bin\Microsoft.Common.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\15.0\Microsoft.Common.targets\ImportBefore\Microsoft.Net.CoreRuntime.ImportBefore.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\15.0\Microsoft.Common.targets\ImportBefore\Microsoft.NetNative.ImportBefore.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\Microsoft\VisualStudio\v15.0\CodeAnalysis\Microsoft.CodeAnalysis.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\15.0\Bin\Microsoft.Xaml.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\15.0\Bin\Microsoft.WorkflowBuildExtensions.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\Microsoft\VisualStudio\v15.0\TeamTest\Microsoft.TeamTest.targets
c:\program files (x86)\microsoft visual studio\2017\professional\Common7\IDE\CommonExtensions\Microsoft\NuGet\NuGet.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\15.0\Microsoft.Common.targets\ImportAfter\Microsoft.Docker.ImportAfter.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\Sdks\Microsoft.Docker.Sdk\build\Microsoft.Docker.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\15.0\Microsoft.Common.targets\ImportAfter\Microsoft.NET.Build.Extensions.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\Microsoft\Microsoft.NET.Build.Extensions\Microsoft.NET.Build.Extensions.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\15.0\Microsoft.Common.targets\ImportAfter\Microsoft.Net.CoreRuntime.ImportAfter.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\15.0\Microsoft.Common.targets\ImportAfter\Microsoft.NetNative.ImportAfter.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\15.0\Microsoft.Common.targets\ImportAfter\Microsoft.NuGet.ImportAfter.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\15.0\Microsoft.Common.targets\ImportAfter\Microsoft.VisualStudio.Azure.Fabric.ServiceProject.ImportAfter.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\Microsoft\VisualStudio\v15.0\Service Fabric Tools\Microsoft.VisualStudio.Azure.Fabric.ServiceProject.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\15.0\Microsoft.Common.targets\ImportAfter\Microsoft.Web.ImportAfter.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\Microsoft\VisualStudio\Managed.Web\Microsoft.Web.IISSupport.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\15.0\Bin\Microsoft.ServiceModel.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\Microsoft\VisualStudio\Razor\Microsoft.NET.Sdk.Razor.DesignTime.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\Microsoft\VisualStudio\v15.0\TypeScript\Microsoft.TypeScript.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\Microsoft\VisualStudio\v15.0\TypeScript\Microsoft.TypeScript.DotNetCore.targets
c:\program files (x86)\microsoft visual studio\2017\professional\MSBuild\Microsoft\VisualStudio\Managed.Web\Microsoft.Web.Designtime.targets

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.
Back to top
BLOG
1 user thanked Der-Albert.com for this useful post.
michaelkroes on 9/2/2018(UTC)
Der-Albert.com
#2 Posted : Wednesday, August 29, 2018 1:42:42 PM(UTC)
Rank: Advanced Member

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

Thanks: 11 times
Was thanked: 55 time(s) in 51 post(s)
I installed VS 2017 Pro (15.8.2), still not working, i installed 3.19.3, still not working.

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 , BuildOutput )
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.




Builds and runs fine locally.
Back to top
BLOG
 |  Edit by user
1 user thanked Der-Albert.com for this useful post.
michaelkroes on 9/2/2018(UTC)
Remco
#3 Posted : Thursday, August 30, 2018 12:07:31 AM(UTC)
Rank: NCrunch Developer

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

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Hi,

Thanks for sharing this issue.

I'm fairly certain this used to work, though it was conditional on the build tools representing themselves as a type of VS installation. It's quite possible that something has changed in the way they install themselves that's now broken this. We'll take a look and will let you know as soon as we know what's going on.
Back to top
Der-Albert.com
#4 Posted : Thursday, August 30, 2018 7:23:24 AM(UTC)
Rank: Advanced Member

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

Thanks: 11 times
Was thanked: 55 time(s) in 51 post(s)
There is something broken on my system and i don't know what.

It worked fine before my vacation with 15.8.previewXYZ Enterprise on the Grid Node and on my Laptop. So now the history what i did.

Within the Vacations (didn't code something only updated systems) i had to change my MSDN Enterprise Subscription to Professional and 15.8 final was out.

So i removed the Previews von the Grid Node and my Laptop, i installed VS2017 Pro (15.8.0) on my Laptop and the Build Tools (15.8.0) in the Grid Node (NCrunch 3.18.2). Did not do some tests.

Vacations over.

Updated everything to 15.8.2. Started Coding, then the error occurred. I reinstalled NCrunch 3.18.2 on the Grid Node (set the Logon User).

Installed VS 2017 Pro 15.8.2 on the Grid node. No missing warnings in the Error Message anymore. I installed 3.19.3 from the forum (Laptop and GridNode). Same Error.

Restarted sometimes, installed 3.19.3 sometimes. Same Error.

Now i removed the VS 2017 Build Tools, same error.

Now i'm stucked.

Quote:

.NET Core SDKs installed:
2.1.202 [C:\Program Files\dotnet\sdk]
2.1.302 [C:\Program Files\dotnet\sdk]
2.1.400 [C:\Program Files\dotnet\sdk]
2.1.401 [C:\Program Files\dotnet\sdk]


It is not working with complex projects, and also not working with simple projects (1 x ASP.NET Core 2.1, 1xTest Project). It does not build the ASP.NET Core 2.1 project.
Back to top
BLOG
1 user thanked Der-Albert.com for this useful post.
michaelkroes on 9/2/2018(UTC)
michaelkroes
#5 Posted : Sunday, September 2, 2018 8:43:33 AM(UTC)
Rank: NCrunch Developer

Groups: Registered
Joined: 9/22/2017(UTC)
Posts: 306
Location: Netherlands

Thanks: 138 times
Was thanked: 73 time(s) in 69 post(s)
Hi,

I've tried to reproduce this issue. I haven't been able to break this on a VM (using the buildtools, with and without VS installed/uninstalled). It looks like your machine is in a state where the com code we use to find the Visual Studio installation is broken. I'm guessing you've already done this, but have you tried repairing the installation?

A way of working around this is setting the environment variable NCrunchVSInstallPath.VS2017 to C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools (Or the path were you've installed it) This should allow use to locate the required msbuild tools.

I hope that that should get you working again.
Back to top
1 user thanked michaelkroes for this useful post.
Der-Albert.com on 9/2/2018(UTC)
Der-Albert.com
#6 Posted : Sunday, September 2, 2018 1:55:35 PM(UTC)
Rank: Advanced Member

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

Thanks: 11 times
Was thanked: 55 time(s) in 51 post(s)
Sorry Michael and Remco. Sorry for wasting your time.

Your last post had the solution in it.

That specific Environment Variable was set to the old Preview Version of VS2017, for whatever reason (i don't remember). I removed it. Now with only the Build Tools it is working so far (for that simple project, will need to check more, but this was the main problem).

A pekcab. But, this leads to a suggestion from me to easier diagnose that kind of problem.

In case of the Build Problem, you give many information as seen in the first post on this thread.

So, if the Environment Variable is set and the path does not exists, point the finger at the user in that message.

At least it is fixed on my side, and if someone else has the same problem, it should be easier to point out ;)
Back to top
BLOG
1 user thanked Der-Albert.com for this useful post.
michaelkroes on 9/3/2018(UTC)
michaelkroes
#7 Posted : Monday, September 3, 2018 6:08:45 AM(UTC)
Rank: NCrunch Developer

Groups: Registered
Joined: 9/22/2017(UTC)
Posts: 306
Location: Netherlands

Thanks: 138 times
Was thanked: 73 time(s) in 69 post(s)
No worries Albert :) Thanks for letting us know!
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.081 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download