Windows Live Messenger add-in fails to read XML on some computers

[Elliot]

I am writing a Windows Live Messenger add-in that reads the content of a XML
file.
However, it does not work(cannot read it) for some computers(I have not
summed up the rule). Do you know what can cause this issue?

It works on both XP & Vista and Messenger version 8.1 & 8.5, so I do not
think it is the matter of OS & Messenger.

Any idea would be appreciated.

[Peter Duniho]

On Wed, 20 Aug 2008 12:11:09 -0700, Elliot <el************ @hotmail.co.uk>
wrote:

I am writing a Windows Live Messenger add-in that reads the content of a
XML file.
However, it does not work(cannot read it) for some computers(I have not
summed up the rule). Do you know what can cause this issue?

There is far too little information in your post for anyone to provide a
suggestion. What does "it does not work" mean? Does it fail to open the
file? Does it fail to read the file? Does it fail to correctly interpret
the file? And regardless of the answers to those questions, what is the
exact nature of the failure? Bad output? An exception? Something else?
In each of those cases, the exact output, exception type and message, etc.
needs to be described in your question. Finally, without a
concise-but-complete code sameple that reliably demonstrates the problem,
even having the answers to the previous questions would be of limited
value. It's possible someone could answer the question without a code
sample, but just as likely not.

Pete

[maximz2005]

On Aug 20, 5:33*pm, "Peter Duniho" <NpOeStPe...@nn owslpianmk.com>
wrote:

On Wed, 20 Aug 2008 12:11:09 -0700, Elliot <elliot_barc... @hotmail.co.uk> *
wrote:

I am writing a Windows Live Messenger add-in that reads the content of a *
XML file.
However, it does not work(cannot read it) for some computers(I have not*
summed up the rule). Do you know what can cause this issue?

Hi,

Please supply a code sample.
If I correctly understand that it gives an exception, please also try
to step through through your code (set a breakpoint somewhere and then
press F11 to go forward). Find when the exception occurs, and indicate
that and the exception details (message, stacktrace, whatever else you
see fit.)
If it does not give you an exception, just simply doesn't return the
current output, step through your code as described earlier in this
post and find what happens to give a bad output.
Posting a code sample will help a lot!

>
There is far too little information in your post for anyone to provide a *
suggestion. *What does "it does not work" mean? *Does it fail to openthe *
file? *Does it fail to read the file? *Does it fail to correctly interpret *
the file? *And regardless of the answers to those questions, what is the *
exact nature of the failure? *Bad output? *An exception? *Somethingelse? *
In each of those cases, the exact output, exception type and message, etc.. *
needs to be described in your question. *Finally, without a *
concise-but-complete code sameple that reliably demonstrates the problem,*
even having the answers to the previous questions would be of limited *
value. *It's possible someone could answer the question without a code *
sample, but just as likely not.

Pete