Exception while loading XslTransform - C# Discussion Boards

Christian Graus14-Jun-07 21:09

Christian Graus

14-Jun-07 21:09

The point of permissions is that they stop you doing things you're not allowed to. Now, if you could change them remotely, what would the point be ?

Christian Graus - Microsoft MVP - C++
Metal Musings - Rex and my new metal blog
"I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )

devesh_code14-Jun-07 21:20

devesh_code

14-Jun-07 21:20

Thanks for your reply..

But tell me how can i change the permission through program and i dont want to change the permission remotely. I want to change the permission by running that application on remote system. is it possible ???

Thanks

Devesh Mishra

ScottM115-Jun-07 1:14

ScottM1

15-Jun-07 1:14

It is possible, I've seen it before, google it.

There are 10 types of people in the world, those who understand binary and those who dont.

Exception while loading XslTransform

Dave Kreskowiak15-Jun-07 3:37

Dave Kreskowiak

15-Jun-07 3:37

That error is saying the account your code is running under doesn't have the permissions to read the registry on the remote machine. You simply cannot get around this.

You have to use an account that the remote machine can authenticate, such as a Domain Admin account in a domain or AD environment.

In a workgroup environment, the account your code runs under must exist on all the machines you want to connect to AND all those accounts must have the same password.

A guide to posting questions on CodeProject[^]

Dave Kreskowiak
Microsoft MVP
Visual Developer - Visual Basic
2006, 2007

Abhi Lahare14-Jun-07 19:58

Abhi Lahare

14-Jun-07 19:58

Hi,

While executing following line i an getting XML exception

<br />
    XslTransform xslt = new XslTransform();<br />
    XPathNavigator navigator = xsldoc.CreateNavigator();/// xsldoc is XPathDocument doc<br />
    try<br />
    {<br />
	xslt.Load(navigator, null, null);<br />
    }<br />
    catch(Exception ex)<br />
    {<br />
        logger.Error("Ex:" + ex.Message + ":" + ex.StackTrace);<br />
    }<br />
			<br />

Sometimes the above code throws exception with stack strace given below.

<br />
(19,2) :<br />
    at System.Xml.Xsl.Compiler.Compile(NavigatorInput input, XmlResolver xmlResolver, Evidence evidence)<br />
   at System.Xml.Xsl.XslTransform.Compile(XPathNavigator stylesheet, XmlResolver resolver, Evidence evidence)<br />
   at System.Xml.Xsl.XslTransform.Load(XPathNavigator stylesheet, XmlResolver resolver, Evidence evidence)<br />

I looked at MSDN for these function which mentions that this will work only on .Net FrameWork 1.1

On my machine. I have 1.1, 1.1 with hotfixes, 2.0 and 3.0. FrameWork installed.

Regards
Abhi Lahare

BinaryFormatter -> Invalid binaryHeader

hansipet14-Jun-07 19:48

14-Jun-07 19:48

Hello,
I have a strange problem. I want to send some objectes over Ethernet (UDP One packet is one object) After that I Deserialize the data, but I get allways an exception that there is an Invalid binaryheader. I don't have any idea how I can solve it.

my code is

<br />
int size = socket.Receive(buf);<br />
BinaryFormatter serializer = new BinaryFormatter();<br />
MemoryStream ms = new MemoryStream(buf,0,size);<br />
ms.Seek(0, SeekOrigin.Begin);<br />
LogMessage logMessage = (LogMessage)serializer.Deserialize(ms);<br />
Console::WriteLine("{0}", logMessage.ToString());<br />
ms.Close();<br />

and the sending function:

<br />
MemoryStream ms = new MemoryStream();<br />
BinaryFormatter serializer = new BinaryFormatter();<br />
<br />
serializer.Serialize(ms, logMessage);<br />
ms.Flush();<br />
ms.Seek(0, SeekOrigin.Begin);<br />
<br />
byte[] data = ms.ToArray();<br />
socket.Send(data);<br />
ms.Close();<br />

I have checked the MemoryStream and there is the whole data available (Sending and receiving)

LogMessage
Best regards
Hansjörg

Soleil couchant14-Jun-07 22:55

Soleil couchant

14-Jun-07 22:55

Are you serializing and deserializing using the same .NET Frameowrk / Operating System?

If you are serializing in, for instance, .NET Framework and the deserializing in .NET Compact Framework, this will be an issue.

Otherwise, you can use the XML Serializer, if platform/framework is your problem

hansipet14-Jun-07 23:19

14-Jun-07 23:19

I use the same computer, same plattform and the both projects are in the same solution from vs2005..
I want to use the binary formatter, because I think it is faster and this is needed in my case.

Best regards
Hansjörg

Rudolf Jan15-Jun-07 0:20

Rudolf Jan

15-Jun-07 0:20

Maybe it is a good idea to use the SOAP serializer first for debugging purposes. It is easier to review to XML then. It is not very difficult to switch back to the binary serializer once it all works.

hansipet15-Jun-07 2:39

15-Jun-07 2:39

with the soap formatter I have one problem. If I serialize my object then I get a NullReferenceException. The problem it seems that it is a DateTime field. If this field is not inside the class (other data are strings) all works fine.

Do you have any idea?

Best regards
Hansjörg

Rudolf Jan18-Jun-07 9:27

Rudolf Jan

18-Jun-07 9:27

I'm not very experienced with this topic. A NullReferenceExpetion means that soemthing is wrong with an object. Likely causes are that you forgot to assign memory (using new) or maybe you try to use an object that no longer exists. Best way to solve this is stepping through the suspected code using the debugger and checking the object values.

hansipet18-Jun-07 19:32

18-Jun-07 19:32

I have checked it...the object that gives the exception is a DateTime value...and this value is okay. I have no idea why...

Best regards
Hansjörg

Rudolf Jan19-Jun-07 10:06

Rudolf Jan

19-Jun-07 10:06

I saw you posted this question in another post. There you mentioned other parameters. Did you check these as well? Also check all other variables you use. Somtimes these errors really are obscure, but it is almost certain you did something wrong. You also may try slight code variations, just to see if these work. Fi replace parameters with constant values, replace the datetime by anonther type of object etc. Just keep trying. It may take you two or three days before you find out.

hansipet19-Jun-07 19:30

19-Jun-07 19:30

I have tried a lot of things and now I have found out the problem. For coding I use c++/cli and there it seems that it is not possible to use the DateTime^, but you have to use DateTime...

Best regards
Hansjörg

leppie15-Jun-07 0:32

leppie

15-Jun-07 0:32

I have seen some funny stuff when closing MemoryStream, remove those .Close() for now. If that is the problem, what does work is placing it in a using block.

xacc.ide-0.2.0.74 - now with C# 3.5 support!

hansipet15-Jun-07 0:55