Hey there, Not sure wether this will help or not, but i've had the exact same problems with RSB when I first started using it last week.
My workstation was Win XP SP3 with MSMQ 3.0 aswell. The source endpoint got weird when the message was received thus reply didn't really work. Have you tried the .NET 3.5 build yet for RSB? Maybe that one is MSMQ 3.0 compatible. I decided to leave a lot of problems behind and just installed a virtual machine running W2K8, .NET 4.0 and MSMQ 4.0 I've also noticed alot of problems when you try to put certain stuff in messages. Some things don't really serialize well. (Such as exceptions, lol) A few minutes ago I tried putting a KeyValuePair<string, object>[] as a property of my message, turns out when its serialized and deserialized the all the kvp's were empty altho they had keys & values assigned before I sent the message. Concerning your code, I don't really get why you still use the source stuff from the CurrentMessageInformation. Like you stated before, it's all weird and that is not good In MSMQ 4.0 whenever I get a message back, the source for CurrentMessageInformation is in the correct format (msmq://localhost/ starbucks.cashier) instead of those weird letters & digits. So changing 'FORMATNAME:PRIVATE=81bf40d1-a337-4ee6-80e8-e198f6b5cdac \0000007b' to 'FormatName:DIRECT=OS:_machinename_\0000007b' isn't going to help. Or does the sourceMessageQueue.QueueName actually returns the correct value? ( as in starbucks.cashier or rhinotesting.testing1 in your case) Kind regards, Dirk On 10 mrt, 13:09, cnash <[email protected]> wrote: > The environment I am using is: > > Rhino Service Bus v1.9.0.0 (although I have also tried 1.8) > Windows XP SP3 (MSMQ 3) > .Net 4.0 -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
