"Invalid Xml" with XmlTransform

[GS]

Hi!

I am getting an "Invalid Xml" exception when I try to load an xsl file
using XslTransform.Lo ad(string url). The Xsl file is valid and works
fine if I just rename the file.

There are some postings with this problem, but none of them have a
solution as yet. If anyone has any ideas on how to resolve this, please
do post.

Thank you.

[John Bailo]

GS wrote:

Hi!

I am getting an "Invalid Xml" exception when I try to load an xsl file
using XslTransform.Lo ad(string url). The Xsl file is valid and works
fine if I just rename the file.

There are some postings with this problem, but none of them have a
solution as yet. If anyone has any ideas on how to resolve this, please
do post.

Thank you.

http://msdn.microsoft.com/library/de...loadtopic2.asp
Is this what you're doing?

using System;
using System.IO;
using System.Xml;
using System.Xml.Xsl;
using System.Xml.XPat h;

public class Sample
{
private const String filename = "books.xml" ;
private const String stylesheet = "output.xsl ";

public static void Main()
{
//Load the stylesheet.
XslTransform xslt = new XslTransform();
xslt.Load(style sheet);

//Load the file to transform.
XPathDocument doc = new XPathDocument(f ilename);

//Create an XmlTextWriter which outputs to the console.
XmlTextWriter writer = new XmlTextWriter(C onsole.Out);

//Transform the file and send the output to the console.
xslt.Transform( doc, null, writer, null);
writer.Close();

}
}

[GS]

Yes, but it fails at ---

xslt.Load(style sheet);

Also the xml and the xsl files are not as simple as in the example.

[John Bailo]

Are you using a try/catch block and can you see the exception?

GS wrote:

Yes, but it fails at ---

xslt.Load(style sheet);

Also the xml and the xsl files are not as simple as in the example.

[John Bailo]

I've seen this happen where you may need to use special entity
characters to replace ampersands and other characters.

SO

<myxml>This & that</myxml>

becomes

<myxml>This &amp; that</myxml>

GS wrote:

Yes, but it fails at ---

xslt.Load(style sheet);

Also the xml and the xsl files are not as simple as in the example.

[GS]

I don't know what the problem was, but I re-installed IIS. It certainly
fixed the problem.

[EvilAbD]

I had a likely problem
this part of code:

I am working with .NET and IIS6

XslTransform xslt = null;
try
{
xslt = new XslTransform();
xslt.Load(currentFile);    
}
catch(Exception Ex)
{
throw new Exception("XSLLoadError", currentFile, Ex.Message);
}
return xslt;

was working for everybody at work exept for me
when the debbuger reach the line

xslt.Load(currentFile);

it was throwing an exception "Invalid xml"

I was testing the xslt, and it was fine.
I test the xslt with an altern program to transform and xml by using a xslt
and it works fine
so that, the problem was not in the xslt file

I have restarted the server several times, deleted temporal files but the same for one specific XSLT the Exception is thrown again. :confused:

I will try your solution about re-install the IIS. :cool:

for now, after being debbuging, I had the idea to rename the XSLT
and in someway, the

xslt.Load(currentFile);

works with my XSLT file :D

my old name was: FIN.IN.AR.Carri er.xslt
my new name: FIN.IN.AR.Carri ers.xslt

As you can see I cannot find a factible reason why was happing this issue
any idea about the real reason because

after it works I return back to the filename that was wich one I had had the problem

and the problem appeared again :confused:

regards

[EvilAbD]

Me again,

About this problem.

I delete the .NET temp files
from:
C:\WINDOWS\Micr osoft.NET\Frame work\v1.1.4322\ Temporary ASP.NET Files

besides I remove temp files by using the menu
Tools > Internet Options > delete Files > Delete All Online Content > OK

I thought that that it could fix my problem with the Invalid Xml, maybe it is a problem,
but that does not work, :mad:

I think there are a problem with the memory
with the cache memory or somethig about it :confused:

finally

I create a new website with another diferent name

I install my application in that new Site

and the problem has gone :p


I think that In some way, IIS or the Net Framework itselft was storing a reference to a wrong file

so that, when you re-install the ISS the reference was clearer
and when I create a new Site, the reference was a new one

when I was using the same site, I think it was using the same reference where the error was

If someone had a better answer for this issue
I will be waiting for it

Thanks