New article that I am pretty happy with, on using NServiceBus and WPF together, good read I think

[Sacha Barber]

http://www.codeproject.com/KB/dotnet/nserviceBusDemo.aspx

--
Sacha Barber
sacha....@gmail.com

[Marlon Grech]

great article dude... quite interesting... 

I have a question though why use NServiceBus and not WCF and have MSMQ as your endpoint? asking this to understand the main difference, never did any NServiceBus stuff so quite new to the framework... 

Regards
Marlon
WPF Blog - http://marlongrech.wordpress.com/
Microsoft MVP for Client App

[Marlon Grech]

P.S Happy anniversary to u and Sarah :)  

Regards
Marlon
WPF Blog - http://marlongrech.wordpress.com/
Microsoft MVP for Client App

[Peter O'Hanlon]

Good job mate. I'll vote once I've finished digesting it all - there's a heck of a lot in it.

--
Peter O'Hanlon

[Michael Brown]

From my understanding NServiceBus is more targeted at (and optimized for) event driven architecture. WCF is more of a generic communications abstraction. While you can do pub/sub with it, it’s optimized for point to point at least that’s the common view. With nServiceBus you can have a distributed mesh of nodes and setup some very interesting message routing very easily. You can do the same with WCF…but it’s not as easy.

 

Besides, I think the goal was more to learn the new framework as opposed to compare/contrast between the two.

[Michael Brown]

Sacha,

Just read through the full article! Great job as always! Josh, this is what I mentioned when we talked about keeping clients in sync with changes to the model. There would be a central server (instead of peer to peer as Sacha used) that all the clients would Subscribe to. All operations would go through the central server that would then notify all clients of the change. As I mentioned, nServiceBus makes it pretty easy to load balance the servers as well (so you can scale out as client needs grow). As I recall, you needed a solution that worked with Silverlight. So you’d have to use the HttpPollingDuplexBinding against an nSB façade.

 

--Mike

 

From: wpf-di...@googlegroups.com [mailto:wpf-di...@googlegroups.com] On Behalf Of Peter O'Hanlon
Sent: Saturday, August 28, 2010 12:47 PM
To: wpf-di...@googlegroups.com
Subject: Re: [WPF Disciples] New article that I am pretty happy with, on using NServiceBus and WPF together, good read I think

 

Good job mate. I'll vote once I've finished digesting it all - there's a heck of a lot in it.

[Daniel Vaughan]

Yes, me too. Looks awesome.

 

 

From: wpf-di...@googlegroups.com [mailto:wpf-di...@googlegroups.com] On Behalf Of Peter O'Hanlon
Sent: Saturday, 28 August 2010 6:47 PM
To: wpf-di...@googlegroups.com
Subject: Re: [WPF Disciples] New article that I am pretty happy with, on using NServiceBus and WPF together, good read I think

 

Good job mate. I'll vote once I've finished digesting it all - there's a heck of a lot in it.

[Sacha Barber]

Marlon

The reason we are looking into using it over WCF, is that we do have a real need to communicate between loads of different apps, some can use WCF some can not, but NServiceBus is compatible with .NET onwards, at present we talk to several systems using MSMQBinding and WCF, but it is a pain, as there is quite a lot to get it working well.

I found with NServiceBus I had it working in about 20 minutes.

Mike

Thanks for your props, I was pretty pleased with this article

Josh

I did do Peer2Peer, but Sub/Sub is actually even easier to get working and set up.

Thanks ye all.

--
Sacha Barber
sacha....@gmail.com

[Sacha Barber]

NServiceBus is compatible with .NET 2 I should have said. Doh

--
Sacha Barber
sacha....@gmail.com

[Marlon Grech]

makes sense...  cool stuff dude... 

Regards
Marlon
WPF Blog - http://marlongrech.wordpress.com/
Microsoft MVP for Client App

On Mon, Aug 30, 2010 at 3:22 PM, Sacha Barber <sacha....@gmail.com> wrote:

[Sacha Barber]

cheers ears

--
Sacha Barber
sacha....@gmail.com