Hello.

I'm in the midst of moving a web application from ASP.NET 1.1 to
ASP.NET 2.0 (framework 3.0), and as part of this move, I am told by
Visual Studio that the XslTransform object is now deprecated, and I
should use XslCompiledTransform. For the most part changing to this
object works fine, however I have noticed in some cases a difference
of behavior that breaks the proper running of my app.

I am using XSL templates to transform XML into HTML to be outputted to
the browser, and in some of my templates I have HTML "script" tags,
like so:

<script ...></script>

Using the old XslTransform object, this was handled just fine.
However, using the new XslCompiledTransform object, instances of these
script tags are reduced to single-tag versions in the output, like so:

<script ... />

Since this syntax is currently not valid HTML, browsers are not
correctly handling this output, and I get lots of javascript errors
and display problems.

Is this expected behavior by the new XslCompiledTransform object? Is
there any way to prevent it from doing this, or do I just need to keep
using the deprecated XslTransform instead?

Thanks!

--Steve