New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
busbina opened this Issue May 16, 2017 · 13 comments

Comments

Projects
None yet
@busbina
Copy link

busbina commented May 16, 2017

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

@morganbr

This comment has been minimized.

Copy link
Contributor

morganbr commented May 18, 2017

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

This comment has been minimized.

Copy link
Contributor

blowdart commented May 18, 2017

@busbina

This comment has been minimized.

Copy link

busbina commented May 19, 2017

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

This comment has been minimized.

Copy link

jamesfarrer commented Jun 28, 2017

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

@tehkyle

This comment has been minimized.

Copy link

tehkyle commented Jun 29, 2017

+1 here as well.

@pankilpatel2

This comment has been minimized.

Copy link

pankilpatel2 commented Mar 29, 2018

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

@stevieg402

This comment has been minimized.

Copy link

stevieg402 commented Jul 10, 2018

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

@carlomilanesi

This comment has been minimized.

Copy link

carlomilanesi commented Jul 11, 2018

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

@nzthiago

This comment has been minimized.

Copy link

nzthiago commented Aug 29, 2018

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

This comment has been minimized.

Copy link
Member

krwq commented Sep 4, 2018

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

@TFTomSun

This comment has been minimized.

Copy link

TFTomSun commented Sep 6, 2018

+1 here as well

@TFTomSun

This comment has been minimized.

Copy link

TFTomSun commented Sep 6, 2018

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

@sharanys

This comment has been minimized.

Copy link

sharanys commented Oct 26, 2018

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment