I didn't say I was using the XslTransform class, I was generically referring to the XslTransform engine in .NET (and this is a .NET 2.0 application). 
  The issue is clearly a problem with the update as my server that does not have the update doesn't produce the bad output but the one with it does.

Here's a real simple example that produces the bad output.


         <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
             <xsl:output method="html" omit-xml-declaration="no"  encoding="ISO-8859-1" />

             <xsl:template match="/">
                 <b>&#0160;</b>
             </xsl:template>

         </xsl:stylesheet>


This generates character xFFFD in the output where it produced a proper space character previously.







Martin Honnen wrote:
> APA wrote:
>> Has anyone seen any problems in the XslTransform engine since the .NET 
>> 2.0 security update?  I use the &#160; character for spaces in some of 
>> my XSL and it is converting them into character #FFFD in the output.
> 
> With .NET 2.0 you should use XslCompiledTransform not XslTransform.
> As for the problem, can you provide a minimal stylesheet, XML input, and 
> code to run the transformation that demonstrates the problem?
> 
>