使用MSMQ - System.Messaging与WCF [英] Using MSMQ - System.Messaging versus WCF

问题描述

我有口的VB 6.0应用程序，以VB.Net（框架3.5）。该应用程序使用MSMQ严重。我试图弄清楚什么是使用WCF超过老好人System.Messaging的优势。是否有任何潜在的搅局者时System.Messaging回事？

I have to port a VB 6.0 app to VB.Net (Framework 3.5). The application uses MSMQ heavily. I'm trying to figure out what are the advantages of using WCF over good ole System.Messaging. Are there any potential showstoppers when going with System.Messaging?

推荐答案

我觉得这句话从<一href="http://blogs.msdn.com/motleyqueue/archive/2007/09/22/system-messaging-versus-wcf-queuing.aspx">Motley队列网站（网络：优秀的链接）总结得非常好：

I think this quote from the "Motley Queue" web site ("web": excellent link!) sums it up best:

*的WCF编程模型是围绕着您的业务运营。有了它，你可以停止管理您的信息交易，设置邮件属性，寻找一个队列的消息，检查南通中远川崎，重试的消息，等等。相反，你可以开始世界思维的业务运营（如CreatePurchaseOrder）和重点方面在你的业务逻辑。 退出乏味到WCF。 *

*The WCF programming model is centered around your business operations. With it, you can stop managing your message transactions, setting message properties, searching for messages in a queue, checking for NACKS, retrying messages, etc. Instead you can start thinking of the world in terms of business operations (e.g. CreatePurchaseOrder) and focus on your business logic. Leave the tedium to WCF. *

这是一个简单地说什么WCF试图完成 - 减轻你很多管道和intricasies的，让您专注于您的业务问题要解决。

That is in a nutshell what WCF tries to accomplish - relieve you of a lot of plumbing and intricasies and let you concentrate on your business problems you want to solve.

我的票是为WCF！ ： - ）

My vote is in for WCF! :-)

马克·

这篇关于使用MSMQ - System.Messaging与WCF的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！