can we use XslTransform for .NET Framework 3.5

Question

0.00/5 (No votes)

See more:

can we use XslTransform for .NET 3.5 as XSLCompiledTransform is taking lots of time to compile the whole XSL StyleSheet. It is taking almost all the memory.

Posted 18-Jun-14 22:42pm

RajaSekhar Korimilli

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Valery Possoz · Accepted Answer · 2014-06-19T10:44:00

Solution 1

Hello,

Yes you can.

http://msdn.microsoft.com/en-us/library/system.xml.xsl.xsltransform(v=vs.90).aspx[^]

XslTransform xslt = new XslTransform();
xslt.Load("http://server/favorite.xsl");
XPathDocument mydata = new XPathDocument("inputdata.xml");
XmlWriter writer = new XmlTextWriter(Console.Out);
xslt.Transform(mydata,null,writer, null);

Valery.

Posted 19-Jun-14 10:44am

Valery Possoz

Comments

RajaSekhar Korimilli 20-Jun-14 0:13am

But this Class has been deprecated from .NET Framework 2.0 to 3.5. Can we still use it?

Valery Possoz 20-Jun-14 14:29pm

Yes you can use it. It is "marked" as deprecated but it is still there... actually it is still there in .net 4.5

Extract form the Microsoft documentation:
The .NET Framework and the common language runtime strive to support backward compatibility (allowing applications that were developed with one version of the .NET Framework to run on the next version of the .NET Framework). This makes it difficult to simply remove a type or a type member. Instead, the .NET Framework indicates that a type or a type member should no longer be used by marking it as obsolete or deprecated. Deprecating a type or a member involves marking it so that developers are aware it will go away and have time to respond to its removal. However, existing code that uses the type or member continues to run in the new version of the .NET Framework.