Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
configure-toolset not respected by msbuild.sh
See original GitHub issueWe set use_installed_dotnet_cli=false in configure-toolset.sh. This is respected by dotnet.sh but not msbuild.sh, which will fall back to the global install.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Visual Studio not respecting msbuild schema
I have created a sample with your code snippet, but it works fine on my side. Since there is no build log, I...
Read more >Unable to find 15.0 toolset in a project with MSBuild in it's ...
Repro steps: Create a project called "MSBuildTest" (or something with msbuild in the name) and reference the Microsoft.Build package.
Read more >MSBuild Toolset (ToolsVersion)
Learn how to use the ToolsVersion attribute in the MSBuild project file to specify a toolset of tasks, targets, and tools to build...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Can you point to an example of the behavior you’re describing? What is
dotnet.sh? That’s not a file provided by Arcade. It’s not really expected that people directly invokemsbuild.sh(but people do it).Fixed in https://github.com/dotnet/arcade/pull/3975.