Runtime: Add <msxsl:script> support to System.Xml.Xsl

[busbina]

In need of this to be supported in order to move onto Core 2.0.

[morganbr]

We need to consider the security implications of Xsl scripting since there are a number of cases where it is not safe to use.

CC @blowdart

[blowdart]

Yea I'd much rather we don't even go here.

A single request doesn't strike me as justification for something so risky in terms of security.

[busbina]

I need it for legacy customer support, it already comes disabled, and I am fine enabling based on customer needs. Without it we are stuck on MSXML 6.0, with no package deployment options.

[jamesfarrer]

+1 for me for this. Also holding back a .NET Core port

[tehkyle]

+1 here as well.

[pankilpatel2]

Same for us. It's holding back a .Net Core port of the project

[stevieg402]

+1 it's also holding back a .Net Core project here.

[carlomilanesi]

Me too. I am developing a Linux solution porting some XSLT files containing JavaScript code. Now I use MSXSL.exe.

[nzthiago]

Have run into a customer porting a BizTalk mapping solution into Azure, trying to run their existing maps from inside Azure Functions, and ran into this same issue with Functions v2 (.NET Core based) while V1 worked fine (netfx based).

What are some alternatives? Remove any scripting from the maps, move the script code back into your main .NET code and edit the output file contents with it?

[krwq]

Current recommendation is to remove any dependency on this feature. We'll update if plans regarding support for this feature change

[TFTomSun]

+1 here as well

[TFTomSun]

@carlomilanesi can u please tell me more about your workaround? Is it possible to transform xslt with scripts on linux with ur solution?

[sharanys]

+1. Please update on the latest developments on this case

[connecsys]

+1 for me too. I have a team that wants to leverage the BizTalk/EIP map designer to create XSLT that is executed in .NET Core. Please let me know if there is another visual designer they can leverage that is compatible with .NET Core.

[hxbergen]

+1 for me too

[mstaal]

I would like this functionality for legacy purposes, but I realized that this concept is just as good, and it actually come with .NET Core as of now:
https://docs.microsoft.com/en-us/dotnet/standard/data/xml/xslt-extension-objects

[mstaal]

For those who may be interested, I have made this small .NET Core example of how to use Microsoft XSLT Extension Objects instead of the msxsl-tag:
https://github.com/mstaal/XsltService/
The example comes with a REST api in the ApiController, the functions are located in XsltFunctions.cs, and the functions are loaded in an Extension Object in XsltTransformation.cs.

[brandonh-msft]

Here's an example doing this in .NET Core v2 from w/in an Azure Function:
https://github.com/brandonh-msft/EmbeddedXsltTestFunction

[terrajobst]

We don't plan on bringing this .NET Framework API to .NET Core. See this announcement for details.