I\'m using a WCF Service with netMsmqBinding and WAS.Everything seems to work well (including remote posting to the queue thanks to stackoverflow community:)).
I have a scenario where large stream of data is to be stored. Which option is better to store the 开发者_如何学编程stream of byte data since we need to store & retrieve the information.
I am trying to send large objects (>30MB) to a MSMQ queue. Due to the large amount of data we are are tring to send the idea was to GZip the objects prior to sending them, then unzipping them on the r
Windows 7 32bit, .NET4.Specifically, when I do this: _queue.Send(mqMessage); return mqMessage.Lo开发者_C百科okupId;
I am tasked with rewriting a series of legacy services (win and web + msmq). Because of the state they are in, I cannot quickly add functionality to them so they \'call home\' to report status/health.
I\'m learning about MSMQ and am successfully using it to queue email and text messages from a consumer-facing ASP.NET MVC website, to be handled by a separate client application.
5 years ago i\'ve developed a program which used MSMQ. Back then, i used the System.Messaging.MessageQueue and the System.Messaging.MessageQueueTransaction to put items on the msmq.
First off, I have no experience with MSMQ. Supposing an invalid path is passed into the constructor for a private MessageQueue object, would it trigger a MessageQueueException when the send method i
I have an application that uses MSMQ that is working very well when both the producer and consumer are on
Hy, all. I have an interesting case. I have tried to create a wcf service-client communication based on netmsmq binding hosted on windows service app.
加载中,请稍侯......