I bought the Professional Sitecore 8 Development book and I am following the Sitecore Helix architecture approach. And following the examples in the book and online I am using Gulp in the Task Runner Explorer window to build and deploy the solution. Often times when I run the 'Publish-Site' Gulp task I see error codes in red that say
MSBuild failed with code 1 . I have no idea what that means or how to troubleshoot it. Can anyone help me understand what that message means and how to troubleshoot it?
Active3 months ago
The MSBuild and Visual Studio Build tasks already add /nr:false to the arguments passed to MSBuild. However, if you invoke MSBuild from your own script, then you would need to specify the argument. However, if you invoke MSBuild from your own script, then you would need to specify the argument. Use Visual Studio for Mac to build apps for mobile, web, and the cloud with Xamarin and.NET Core, as well as games with Unity. Download the Current Release of Visual Studio for Mac To learn more about Visual Studio for Mac, see Mac System Requirements and Mac Platform Targeting and Compatibility. May 07, 2018 If you have any trouble, you can report a problem from inside the IDE on both Visual Studio and Visual Studio for Mac. To track issues, ask questions and find answers, explore the Visual Studio Developer Community. I am trying to run a sln package on TeamCity on a Mac. Does Visual Studio need to be installed on the Mac itself in order to fulfill the. CESARDELATORRE changed the title from Build fails on Visual Studio for Mac to [Bug in VS for Mac] Build fails on Visual Studio for Mac Jun 15, 2018.
Here is a screen shot:
Here is the code from my gulpfile.js
![]()
EDIT:I also noticed that when I do a rebuild of the entire solution that I get a few warnings about versions of System.Web.Mvc. Below is the text of the warning in Visual Studio:
8> No way to resolve conflict between 'System.Web.Mvc, Version=5.2.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' and 'System.Web.Mvc, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. Choosing 'System.Web.Mvc, Version=5.2.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' arbitrarily. https://ojqzwdl.weebly.com/blog/fl-studio-for-mac-crack. 8> Consider app.config remapping of assembly 'System.Web.Mvc, Culture=neutral, PublicKeyToken=31bf3856ad364e35' from Version '3.0.0.0' [] to Version '5.2.3.0' [C:ProjectsSitecoreDevFoundationIocSitecoreDev.Foundation.IocbinSystem.Web.Mvc.dll] to solve conflict and get rid of warning. 8>C:Program Files (x86)MSBuild14.0binMicrosoft.Common.CurrentVersion.targets(1820,5): warning MSB3247: Found conflicts between different versions of the same dependent assembly. In Visual Studio, double-click this warning (or select it and press Enter) to fix the conflicts; otherwise, add the following binding redirects to the 'runtime' node in the application configuration file: 8> SitecoreDev.Foundation.Repository -> C:ProjectsSitecoreDevFoundationRepositorySitecoreDev.Foundation.RepositorybinSitecoreDev.Foundation.Repository.dll
I believe that what this is telling me is that I need to add some assembly binding redirection to the web.config of the SitecoreDev.Foundation.Repository project to resolve this. However I am not completely sure how to accomplish this in the Helix architecture. If I understand correctly I don't want to have a web.config file in any of my projects. If I do then it will overwrite the Sitecore web.config file when it copies files from the dev root to the web root. Right? So I'm not sure how to fix problems like this in a particular project in my solution.
Corey Burnett
Corey BurnettCorey Burnett
1,75722 gold badges1010 silver badges2828 bronze badges
3 Answers
I'm also going through the Professional Sitecore 8 Development book and ran into the same issue. Not sure if you found the fix but thought I'd share my findings. I'm using Visual Studio 2017 Professional (toolsVersion = 15) and it turns out that gulp-msbuild doesn't support VS 2017. I made the following edits to the gulp-msbuild files to make this work:
SolutionRoot/node_modules/gulp-msbuild/lib/constants.js:
Iskysoft itube studio for windows. Modified the MSBUILD_VERSIONS from ..
to this ..
SolutionRoot/node_modules/gulp-msbuild/lib/msbuild-finder.js:
I added the following starting at line 31 ..
I'm sure there are more elements in that path that could/should be parameterized but I'm just interested in getting this to work for this project. After I made these changes I had to reboot and then running the 'Publish-Site' task worked as expected.
Finally, I updated my gulpfile.js to look like this:
Notice the two extra parameters:
VisualStudioVersion and toolsVersion .
I hope that helps.
Cheers
ChesterCChesterC
Please make sure you have the Latest MS build version tools.
you can get the Latest versions from https://www.visualstudio.com/downloads/#build-tools-for-visual-studio-2017
Recommended for sitecore is to use Visual Studio 2017 and Build Tools For Visual Studio 2017. You can also use offline installer by pointing to the directory and running this command.
vs_buildtools.exe --add Microsoft.VisualStudio.Workload.MSBuildTools --quiet
Then run
npm uninstall -g node-gyp
npm install -g node-gyp
Making sure that those node libs are not affected. Hope this helps!
Sitecore SamSitecore Sam
92311 gold badge44 silver badges2525 bronze badges
I followed solution by @sitecore-sam and install build tools v2019 (current version). This installs only Roslyn build tools locally (C:Program Files (x86)Microsoft Visual Studio2019BuildToolsMSBuild15.0BinRoslyn). But gulp taks was keep looking for 'C:Program Files (x86)Microsoft Visual Studio2019BuildToolsMSBuild15.0Binamd64'.
Solution that worked for me was: I copied the amd64 folder from VS2017 Ent edition folders. This is not proper solution but as I could not find a way to forse to install a smd64 version of build tools I just copied the whole folder on required location.
The logicof finder explained by @ChesterC can be found here
Sanjay ZalkeSanjay Zalke
Not the answer you're looking for? Browse other questions tagged helixgulp or ask your own question.
The Microsoft Build Engine is a platform for building applications. This engine, which is also known as MSBuild, provides an XML schema for a project file that controls how the build platform processes and builds software. Visual Studio uses MSBuild, but MSBuild does not depend on Visual Studio. By invoking msbuild.exe on your project or solution file, you can orchestrate and build products in environments where Visual Studio isn't installed.
For more information on MSBuild, see the MSBuild documentation on docs.microsoft.com.
Build Status
The current development branch is
master . It builds for .NET Core and the full desktop .NET framework. Changes in master will go into the next majorupdate of MSBuild.
Cracked fl studio for mac. We have entered stabilization for the 15.6 release (corresponding to Visual Studio 15.6) in the
vs15.6 branch.
Source code
BuildingBuilding MSBuild with Visual Studio 2017
For the full supported experience, you will need to have Visual Studio 2017.
To get started on Visual Studio 2017:
Building MSBuild in Unix (Mac & Linux)
MSBuild can be run on Unix systems that support .NET Core. Set-up instructions can be viewed on the wiki: Building Testing and Debugging on .Net Core MSBuild
Localization
You can turn on localized builds via the
/p:LocalizedBuild=true command line argument. For more information on localized builds and how to make contributions to MSBuild's translations, see our localization wiki
How to Engage, Contribute and Provide Feedback
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.
Getting Started
Before you contribute, please read through the contributing and developer guides to get an idea of what kinds of pull requests we will or won't accept.
Looking for something to work on? This list of up for grabs issues is a great place to start.
Visual Studio For Mac Tutorial
You are also encouraged to start a discussion by filing an issue or creating a gist.
MSBuild Components
LicenseMsbuild Fail Visual Studio For Mac Unknown
MSBuild is licensed under the MIT license.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2020
Categories |