XmlPoke task not available in .NET Core
See original GitHub issueRepro:
<Project>
<Target Name="Build">
<XmlPoke />
</Target>
</Project>
dotnet msbuild /t:Build
Error
poke.proj(3,7): error MSB4062: The “Microsoft.Build.Tasks.XmlPoke” task could not be loaded from the assembly Microsoft.Build.Tasks.Core, Version=15.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a. 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.
Expected Same behavior as MSBuild.exe (full framework)
Details dotnet.exe version: 1.0.0-rc4-004842 MSBuild version: 15.1.548.43366
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
XmlPoke Task - MSBuild
Learn how MSBuild uses the XmlPoke task to set values as specified by an XPath query into an XML file.
Read more >Use of XmlPoke in project file to update source file has ...
1 Answer. Solution is to avoid changing any source files during a msbuild. Instead use a pre-build task to make any source changes...
Read more >Appending nodes in XML files with xmlpeek and xmlpoke ...
This little NAnt task let's you replace a node (or nodes) in an XML file. Trouble is that's what it's designed to do....
Read more >LC Task in .NET Core Projects
NET Core, the LC task is not supported or fails. This article explains how to compile the licenses successfully.
Read more >Using Gulp to Build and Deploy .NET Apps on Windows
I've been using Grunt to build and deploy .NET apps for about a year now. Its a huge improvement over Rake and the...
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

We should bring them back though. We can count this as a vote for pushing this one earlier in the list.
Could have been missing APIs, could have been “not used in our selfhost or the corefx repo and thus we never noticed it wasn’t there”. We should make sure anything missing in vNext is missing for a good reason.
We already reference
System.Xml.XmlDocumentwhich depends onSystem.Xml.XPathandSystem.Xml.XPath.XmlDocument. So having them compiled in just worked. I’ve submitted a PR to see how it does on non-Windows…