Microsoft.Web.XmlTransform
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
dotnet-maestro[bot] 7f4a3dc7c5
[main] Source code updates from dotnet/dotnet (#630)
22 hours ago
.config Fix TSA Options (#610) 8 months ago
eng [main] Source code updates from dotnet/dotnet (#630) 22 hours ago
src/Microsoft.Web.XmlTransform Remove unnecessary CA2022 suppressions (#621) 2 months ago
tests/Microsoft.Web.XmlTransform.Tests Update Microsoft.Web.XmlTransform.Tests.csproj (#557) 1 year ago
.editorconfig Add copyright header to all c# source files 2 years ago
.gitattributes add lf line ending for *.sh files 3 years ago
.gitignore Moving the repo to use Arcade Sdk for building (#19) 6 years ago
CODE-OF-CONDUCT.md Link Code of Conduct 5 years ago
CONTRIBUTING.md Fix links to Code of Conduct 5 years ago
Directory.Build.props [main] Source code updates from dotnet/dotnet (#629) 2 weeks ago
Directory.Build.targets Clean-up xdt repository (#503) 2 years ago
LICENSE.txt Updating the license to MIT 2 years ago
NuGet.config Enable NuGetAudit and perform clean-up (#604) 9 months ago
README.md Fix links to Code of Conduct 5 years ago
azure-pipelines-pr.yml [main] Update dependencies from dotnet/arcade (#620) 2 months ago
azure-pipelines.yml Remove explicitly setting tsaoptions.json path (#623) 2 months ago
build.cmd Moving the repo to use Arcade Sdk for building (#19) 6 years ago
build.sh Moving the repo to use Arcade Sdk for building (#19) 6 years ago
global.json [main] Source code updates from dotnet/dotnet (#630) 22 hours ago
xdt.sln Enable FlagNetStandard1XDependencies switch (#509) 2 years ago

README.md

Microsoft Xml Document Transformation (XDT)

Microsoft Xml Document Transformation (XDT) enables transforming XML files. This is the same technology used to transform web.config files in .NET CLI and Visual Studio.

How to Engage, Contribute, and Give Feedback

Some of the best ways to contribute are to try things out, file issues, join in design conversations, and make pull-requests.

  • Check out the contributing page to see the best places to log issues and start discussions.

Reporting security issues and bugs

Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) secure@microsoft.com. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.