Multiple custom emoticons do not transmit properly

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Send a message containing more than one custom emoticon (using 
SendEmoticonDefinitions) from MSNPSharp.

What is the expected output? What do you see instead?
The expected output is multiple custom emoticons visible in the remote 
client (Live Messenger). Instead, at most one is visible, and sometimes 
none are visible.

What version of the product are you using? On what operating system?
Rev 461, Windows XP Pro.

Please provide any additional information below.
I traced through this a bit and couldn't see an issue with the 
SendEmoticonDefinitions code path, so I'm assuming it must be a problem in 
the P2P invitation request / send mechanism. The good news is usually one 
emoticon shows up. On a related note, I tried out the "Emoticon Test" 
button, and it doesn't seem to work (not sure if it was completed?). It  
causes a little white square placeholder to appear, but not the emoticon.

Also, after trying to send multiple custom emoticons, the remote client 
(Live Messenger) sends an ANS command to MSNPSharp every 60 seconds which 
opens a session and causes SBMessageHandler.ProcessInvitations to get 
called (there's no invitations to process though). Thirty seconds later, 
the session times out, and another thirty seconds later, the process starts 
over again.

Original issue reported on code.google.com by its....@gmail.com on 3 Nov 2008 at 11:45

[GoogleCodeExporter]

Update: I must have confused Live Messenger, I signed out and back in and then 
the 
emoticon test from the DotMSNClient started working, and has continued to work. 
I was 
even able to send multiple custom emoticons from it without any problem.

After struggling further with the same issue in my own project, I finally 
deleted the 
output directory of the referenced MSNPSharp project and rebuilt my client. It 
now 
works, so this issue can be closed - I must have been inadvertently working 
against 
an older codebase.

Original comment by its....@gmail.com on 4 Nov 2008 at 1:30

[GoogleCodeExporter]

Any way, thanks for your reporting.

Original comment by freezing...@gmail.com on 4 Nov 2008 at 3:26

• Changed state: Invalid

[GoogleCodeExporter]

Original comment by hepha...@gmail.com on 23 Jan 2009 at 5:36