XslTransform in .NET v1.1

[George Durzi]

I know this has changed greatly since v1.0. I'm converting a small portion
of my application where I do a transformation.
The error happens on this line:
oXslTransform.Load(XslPath + DataSourceName + ".xsl", oXmlUrlResolver);
ex.Message gives me: "Invalid Site"
ex.InnerException is empty

I've verified that XslPath + DataSourceName + ".xsl" is giving me the
correct path to the stylesheet in the format:

\\servername\e$\XslPath\StylesheetName.xsl

Here's my code

string ReportPath = ReportsFilePath + DataSourceName + TimePeriodSuffix
+ PreferredEmailFormat;
// Create a FileStream to write with
System.IO.FileStream oFileStream = new System.IO.FileStream(ReportPath,
System.IO.FileMode.Create);
// Create an XmlTextWriter for the FileStream
System.Xml.XmlTextWriter oXmlTextWriter = new
System.Xml.XmlTextWriter(oFileStream, System.Text.Encoding.Unicode);

try
{
// Create an XmlDataDocument from the ReportData DataSet parameter
XmlDataDocument oXmlDataDocument = new XmlDataDocument(ReportData);

// Set up the transformation
System.Xml.Xsl.XslTransform oXslTransform = new
System.Xml.Xsl.XslTransform();

// Load the Xsl and Transform
XmlUrlResolver oXmlUrlResolver = new XmlUrlResolver();
oXmlUrlResolver.Credentials = CredentialCache.DefaultCredentials;
oXslTransform.Load(XslPath + DataSourceName + ".xsl", oXmlUrlResolver);
// Xsl Path is class variable
oXslTransform.Transform(oXmlDataDocument, null, oXmlTextWriter,
oXmlUrlResolver);

// Close the XmlTextWriter object
oXmlTextWriter.Close();

return ReportPath;
}
catch (System.Exception ex)
{
oXmlTextWriter.Close();
System.IO.File.Delete(ReportPath);
throw (ex);
}

[George Durzi]

There must be some sort of rights issue. The code below works perfectly when
my Xsl is on a local drive, for example e:\Xsl\MyStyleSheet.Xsl

I get the "Invalid Site" error when my stylesheet is being referenced as
\\server\e$\Xsl\MyStyleSheet.Xsl

"George Durzi" <gd****@hotmail.com> wrote in message
news:eR**************@tk2msftngp13.phx.gbl...

I know this has changed greatly since v1.0. I'm converting a small portion
of my application where I do a transformation.
The error happens on this line:
oXslTransform.Load(XslPath + DataSourceName + ".xsl", oXmlUrlResolver); ex.Message gives me: "Invalid Site"
ex.InnerException is empty

I've verified that XslPath + DataSourceName + ".xsl" is giving me the
correct path to the stylesheet in the format:

\\servername\e$\XslPath\StylesheetName.xsl

Here's my code

string ReportPath = ReportsFilePath + DataSourceName + TimePeriodSuffix + PreferredEmailFormat;
// Create a FileStream to write with
System.IO.FileStream oFileStream = new System.IO.FileStream(ReportPath, System.IO.FileMode.Create);
// Create an XmlTextWriter for the FileStream
System.Xml.XmlTextWriter oXmlTextWriter = new
System.Xml.XmlTextWriter(oFileStream, System.Text.Encoding.Unicode);

try
{
// Create an XmlDataDocument from the ReportData DataSet parameter
XmlDataDocument oXmlDataDocument = new XmlDataDocument(ReportData);

// Set up the transformation
System.Xml.Xsl.XslTransform oXslTransform = new
System.Xml.Xsl.XslTransform();

// Load the Xsl and Transform
XmlUrlResolver oXmlUrlResolver = new XmlUrlResolver();
oXmlUrlResolver.Credentials = CredentialCache.DefaultCredentials;
oXslTransform.Load(XslPath + DataSourceName + ".xsl", oXmlUrlResolver); // Xsl Path is class variable
oXslTransform.Transform(oXmlDataDocument, null, oXmlTextWriter,
oXmlUrlResolver);

// Close the XmlTextWriter object
oXmlTextWriter.Close();

return ReportPath;
}
catch (System.Exception ex)
{
oXmlTextWriter.Close();
System.IO.File.Delete(ReportPath);
throw (ex);
}

[Oliver]

It sounds like the UNC share doesn't know or recognize the ASPNET account or
whoever it is impersonating. You might want to check the permissions on the
share.
"George Durzi" <gd****@hotmail.com> wrote in message
news:u9**************@TK2MSFTNGP10.phx.gbl...

There must be some sort of rights issue. The code below works perfectly when my Xsl is on a local drive, for example e:\Xsl\MyStyleSheet.Xsl

I get the "Invalid Site" error when my stylesheet is being referenced as
\\server\e$\Xsl\MyStyleSheet.Xsl

"George Durzi" <gd****@hotmail.com> wrote in message
news:eR**************@tk2msftngp13.phx.gbl...

I know this has changed greatly since v1.0. I'm converting a small portion of my application where I do a transformation.
The error happens on this line:
oXslTransform.Load(XslPath + DataSourceName + ".xsl",

oXmlUrlResolver);

ex.Message gives me: "Invalid Site"
ex.InnerException is empty

I've verified that XslPath + DataSourceName + ".xsl" is giving me the
correct path to the stylesheet in the format:

\\servername\e$\XslPath\StylesheetName.xsl

Here's my code

string ReportPath = ReportsFilePath + DataSourceName +

TimePeriodSuffix

+ PreferredEmailFormat;
// Create a FileStream to write with
System.IO.FileStream oFileStream = new

System.IO.FileStream(ReportPath,

System.IO.FileMode.Create);
// Create an XmlTextWriter for the FileStream
System.Xml.XmlTextWriter oXmlTextWriter = new
System.Xml.XmlTextWriter(oFileStream, System.Text.Encoding.Unicode);

try
{
// Create an XmlDataDocument from the ReportData DataSet parameter
XmlDataDocument oXmlDataDocument = new XmlDataDocument(ReportData);

// Set up the transformation
System.Xml.Xsl.XslTransform oXslTransform = new
System.Xml.Xsl.XslTransform();

// Load the Xsl and Transform
XmlUrlResolver oXmlUrlResolver = new XmlUrlResolver();
oXmlUrlResolver.Credentials = CredentialCache.DefaultCredentials;
oXslTransform.Load(XslPath + DataSourceName + ".xsl",

oXmlUrlResolver);

// Xsl Path is class variable
oXslTransform.Transform(oXmlDataDocument, null, oXmlTextWriter,
oXmlUrlResolver);

// Close the XmlTextWriter object
oXmlTextWriter.Close();

return ReportPath;
}
catch (System.Exception ex)
{
oXmlTextWriter.Close();
System.IO.File.Delete(ReportPath);
throw (ex);
}

[George Durzi]

The ASPNET account has full control of the whole virtual directory and I am
still experiencing this error :(

Back to square one.

"Oliver" <DE*******************@hotmail.com> wrote in message
news:OZ**************@tk2msftngp13.phx.gbl...

It sounds like the UNC share doesn't know or recognize the ASPNET account or whoever it is impersonating. You might want to check the permissions on the share.
"George Durzi" <gd****@hotmail.com> wrote in message
news:u9**************@TK2MSFTNGP10.phx.gbl...

There must be some sort of rights issue. The code below works perfectly

when

my Xsl is on a local drive, for example e:\Xsl\MyStyleSheet.Xsl

I get the "Invalid Site" error when my stylesheet is being referenced as
\\server\e$\Xsl\MyStyleSheet.Xsl

"George Durzi" <gd****@hotmail.com> wrote in message
news:eR**************@tk2msftngp13.phx.gbl...

I know this has changed greatly since v1.0. I'm converting a small portion of my application where I do a transformation.
The error happens on this line:
oXslTransform.Load(XslPath + DataSourceName + ".xsl",

oXmlUrlResolver);

ex.Message gives me: "Invalid Site"
ex.InnerException is empty

I've verified that XslPath + DataSourceName + ".xsl" is giving me the
correct path to the stylesheet in the format:

\\servername\e$\XslPath\StylesheetName.xsl

Here's my code

string ReportPath = ReportsFilePath + DataSourceName +

TimePeriodSuffix

+ PreferredEmailFormat;
// Create a FileStream to write with
System.IO.FileStream oFileStream = new

System.IO.FileStream(ReportPath,

System.IO.FileMode.Create);
// Create an XmlTextWriter for the FileStream
System.Xml.XmlTextWriter oXmlTextWriter = new
System.Xml.XmlTextWriter(oFileStream, System.Text.Encoding.Unicode);

try
{
// Create an XmlDataDocument from the ReportData DataSet parameter XmlDataDocument oXmlDataDocument = new XmlDataDocument(ReportData);
// Set up the transformation
System.Xml.Xsl.XslTransform oXslTransform = new
System.Xml.Xsl.XslTransform();

// Load the Xsl and Transform
XmlUrlResolver oXmlUrlResolver = new XmlUrlResolver();
oXmlUrlResolver.Credentials = CredentialCache.DefaultCredentials;
oXslTransform.Load(XslPath + DataSourceName + ".xsl",

oXmlUrlResolver);

// Xsl Path is class variable
oXslTransform.Transform(oXmlDataDocument, null, oXmlTextWriter,
oXmlUrlResolver);

// Close the XmlTextWriter object
oXmlTextWriter.Close();

return ReportPath;
}
catch (System.Exception ex)
{
oXmlTextWriter.Close();
System.IO.File.Delete(ReportPath);
throw (ex);
}

[Oliver]

But is ASP.NET impersonating someone who doesn't have rights... like the
IUSR_<machinename> account?
"George Durzi" <gd****@hotmail.com> wrote in message
news:%2***************@TK2MSFTNGP11.phx.gbl...

The ASPNET account has full control of the whole virtual directory and I am still experiencing this error :(

Back to square one.

"Oliver" <DE*******************@hotmail.com> wrote in message
news:OZ**************@tk2msftngp13.phx.gbl...

It sounds like the UNC share doesn't know or recognize the ASPNET account

or

whoever it is impersonating. You might want to check the permissions on

the

share.
"George Durzi" <gd****@hotmail.com> wrote in message
news:u9**************@TK2MSFTNGP10.phx.gbl...

There must be some sort of rights issue. The code below works perfectly

when

my Xsl is on a local drive, for example e:\Xsl\MyStyleSheet.Xsl

I get the "Invalid Site" error when my stylesheet is being referenced

as \\server\e$\Xsl\MyStyleSheet.Xsl

"George Durzi" <gd****@hotmail.com> wrote in message
news:eR**************@tk2msftngp13.phx.gbl...
> I know this has changed greatly since v1.0. I'm converting a small

portion

> of my application where I do a transformation.
> The error happens on this line:
> oXslTransform.Load(XslPath + DataSourceName + ".xsl",
oXmlUrlResolver);
> ex.Message gives me: "Invalid Site"
> ex.InnerException is empty
>
> I've verified that XslPath + DataSourceName + ".xsl" is giving me the > correct path to the stylesheet in the format:
>
> \\servername\e$\XslPath\StylesheetName.xsl
>
> Here's my code
>
> string ReportPath = ReportsFilePath + DataSourceName +
TimePeriodSuffix
> + PreferredEmailFormat;
> // Create a FileStream to write with
> System.IO.FileStream oFileStream = new
System.IO.FileStream(ReportPath,
> System.IO.FileMode.Create);
> // Create an XmlTextWriter for the FileStream
> System.Xml.XmlTextWriter oXmlTextWriter = new
> System.Xml.XmlTextWriter(oFileStream, System.Text.Encoding.Unicode);
>
> try
> {
> // Create an XmlDataDocument from the ReportData DataSet

parameter > XmlDataDocument oXmlDataDocument = new XmlDataDocument(ReportData); >
> // Set up the transformation
> System.Xml.Xsl.XslTransform oXslTransform = new
> System.Xml.Xsl.XslTransform();
>
> // Load the Xsl and Transform
> XmlUrlResolver oXmlUrlResolver = new XmlUrlResolver();
> oXmlUrlResolver.Credentials = CredentialCache.DefaultCredentials; > oXslTransform.Load(XslPath + DataSourceName + ".xsl",
oXmlUrlResolver);
> // Xsl Path is class variable
> oXslTransform.Transform(oXmlDataDocument, null, oXmlTextWriter,
> oXmlUrlResolver);
>
> // Close the XmlTextWriter object
> oXmlTextWriter.Close();
>
> return ReportPath;
> }
> catch (System.Exception ex)
> {
> oXmlTextWriter.Close();
> System.IO.File.Delete(ReportPath);
> throw (ex);
> }
>
>

[George Durzi]

This is actually a Console application. Would Console applications also run
as the ASPNET account?
"Oliver" <DE*******************@hotmail.com> wrote in message
news:OU**************@TK2MSFTNGP10.phx.gbl...

But is ASP.NET impersonating someone who doesn't have rights... like the
IUSR_<machinename> account?
"George Durzi" <gd****@hotmail.com> wrote in message
news:%2***************@TK2MSFTNGP11.phx.gbl...

The ASPNET account has full control of the whole virtual directory and I am

still experiencing this error :(

Back to square one.

"Oliver" <DE*******************@hotmail.com> wrote in message
news:OZ**************@tk2msftngp13.phx.gbl...

It sounds like the UNC share doesn't know or recognize the ASPNET account

or

whoever it is impersonating. You might want to check the permissions on

the

share.
"George Durzi" <gd****@hotmail.com> wrote in message
news:u9**************@TK2MSFTNGP10.phx.gbl...
> There must be some sort of rights issue. The code below works

perfectly when
> my Xsl is on a local drive, for example e:\Xsl\MyStyleSheet.Xsl
>
> I get the "Invalid Site" error when my stylesheet is being

referenced as > \\server\e$\Xsl\MyStyleSheet.Xsl
>
> "George Durzi" <gd****@hotmail.com> wrote in message
> news:eR**************@tk2msftngp13.phx.gbl...
> > I know this has changed greatly since v1.0. I'm converting a small
portion
> > of my application where I do a transformation.
> > The error happens on this line:
> > oXslTransform.Load(XslPath + DataSourceName + ".xsl",
> oXmlUrlResolver);
> > ex.Message gives me: "Invalid Site"
> > ex.InnerException is empty
> >
> > I've verified that XslPath + DataSourceName + ".xsl" is giving me the > > correct path to the stylesheet in the format:
> >
> > \\servername\e$\XslPath\StylesheetName.xsl
> >
> > Here's my code
> >
> > string ReportPath = ReportsFilePath + DataSourceName +
> TimePeriodSuffix
> > + PreferredEmailFormat;
> > // Create a FileStream to write with
> > System.IO.FileStream oFileStream = new
> System.IO.FileStream(ReportPath,
> > System.IO.FileMode.Create);
> > // Create an XmlTextWriter for the FileStream
> > System.Xml.XmlTextWriter oXmlTextWriter = new
> > System.Xml.XmlTextWriter(oFileStream,

System.Text.Encoding.Unicode); > >
> > try
> > {
> > // Create an XmlDataDocument from the ReportData DataSet

parameter

> > XmlDataDocument oXmlDataDocument = new

XmlDataDocument(ReportData);

> >
> > // Set up the transformation
> > System.Xml.Xsl.XslTransform oXslTransform = new
> > System.Xml.Xsl.XslTransform();
> >
> > // Load the Xsl and Transform
> > XmlUrlResolver oXmlUrlResolver = new XmlUrlResolver();
> > oXmlUrlResolver.Credentials =

CredentialCache.DefaultCredentials; > > oXslTransform.Load(XslPath + DataSourceName + ".xsl",
> oXmlUrlResolver);
> > // Xsl Path is class variable
> > oXslTransform.Transform(oXmlDataDocument, null, oXmlTextWriter, > > oXmlUrlResolver);
> >
> > // Close the XmlTextWriter object
> > oXmlTextWriter.Close();
> >
> > return ReportPath;
> > }
> > catch (System.Exception ex)
> > {
> > oXmlTextWriter.Close();
> > System.IO.File.Delete(ReportPath);
> > throw (ex);
> > }
> >
> >
>
>

[Oliver]

Hi George,

I think a console application would run as the logged on user unless
configured to run as someone else.
"George Durzi" <gd****@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...

This is actually a Console application. Would Console applications also run as the ASPNET account?

[George Durzi]

I'm running the Console app on my machine in debug mode logged on with my
user id which is an enterprise admin on our domain.

When I point to my test Xsls locally on my machine (they're accessible at
e:\inetpub\wwwroot\MyApp\Xsl) everything runs fine. But when I switch to my
production Xsls accessible at \\server\e$\inetpub\etc ... I get that error.

I'll play around with it a little more tomorrow having it run under
different Ids. I'll post my success/failure here.

Amazing how this damn XmlResolver has turned 1 line of code into 5

"Oliver" <DE*******************@hotmail.com> wrote in message
news:eI**************@TK2MSFTNGP11.phx.gbl...

Hi George,

I think a console application would run as the logged on user unless
configured to run as someone else.
"George Durzi" <gd****@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...

This is actually a Console application. Would Console applications also

run

as the ASPNET account?

[Bret Mulvey [MS]]

..NET 1.1 changed how XslTransform handles security. If I understand the docs
correctly, .NET 1.0 ran XSLT's (scripts embedded in XSLT's, access from
document() Xpath function, etc.) in a fully-trusted way. .NET 1.1 restricts
the level of trust by default. Remote files are less trusted than local
files, so you may be getting a security error because of that.

If you trust the remote XSLT, you give XsltTransform the same level of trust
as the calling assembly by passing this.GetType().Assembly.Evidence to the
evidence parameter of the Load method.

"Oliver" <DE*******************@hotmail.com> wrote in message
news:eI**************@TK2MSFTNGP11.phx.gbl...

Hi George,

I think a console application would run as the logged on user unless
configured to run as someone else.
"George Durzi" <gd****@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...

This is actually a Console application. Would Console applications also

run

as the ASPNET account?

[George Durzi]

Bret and Oliver
Thank you both for your help. I've gotten this to work.

"Bret Mulvey [MS]" <br***@online.microsoft.com> wrote in message
news:BC6tb.1329$Dw6.12720@attbi_s02...

.NET 1.1 changed how XslTransform handles security. If I understand the docs correctly, .NET 1.0 ran XSLT's (scripts embedded in XSLT's, access from
document() Xpath function, etc.) in a fully-trusted way. .NET 1.1 restricts the level of trust by default. Remote files are less trusted than local
files, so you may be getting a security error because of that.

If you trust the remote XSLT, you give XsltTransform the same level of trust as the calling assembly by passing this.GetType().Assembly.Evidence to the
evidence parameter of the Load method.

"Oliver" <DE*******************@hotmail.com> wrote in message
news:eI**************@TK2MSFTNGP11.phx.gbl...

Hi George,

I think a console application would run as the logged on user unless
configured to run as someone else.
"George Durzi" <gd****@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...

This is actually a Console application. Would Console applications

also run

as the ASPNET account?

[Oliver]

Good to hear that George. What was it?
"George Durzi" <gd****@hotmail.com> wrote in message
news:OS**************@TK2MSFTNGP09.phx.gbl...

Bret and Oliver
Thank you both for your help. I've gotten this to work.

[Gerald]

So, George, What's the SOLUTION!????

From http://www.developmentnow.com/g/8_20...--NET-v1-1.htm

Posted via DevelopmentNow.com Groups
http://www.developmentnow.com