Closed baralong closed 11 years ago
Cool - Awesome!
Would updating to the lastest version EasyNetQ cause you any problems? I would like to move to the latest.
The dependencies would look like this
EasyNetQ" version="0.14.4.126" Microsoft.AspNet.SignalR.Core" version="1.1.3" Newtonsoft.Json" version="4.5.11" RabbitMQ.Client" version="3.1.1"
Mark
That looks great to me, I'm also using MassTransit so I ended up having to hunt around for some old versions to make sure everything played nicely.
BTW I got the new stamp exchange running in our staging environment, our sysadmin was glad to be able to revoke our access to the root host. Thanks again for the fast fix.
Cheers, Doug. On Oct 11, 2013 5:05 PM, "Mark deVilliers" notifications@github.com wrote:
Cool - Awesome!
Would updating to the lastest version EasyNetQ cause you any problems? I would like to move to the latest.
The dependencies would look like this
EasyNetQ" version="0.14.4.126" Microsoft.AspNet.SignalR.Core" version="1.1.3" Newtonsoft.Json" version="4.5.11" RabbitMQ.Client" version="3.1.1"
Mark
— Reply to this email directly or view it on GitHubhttps://github.com/mdevilliers/SignalR.RabbitMq/issues/15#issuecomment-26123729 .
I've updated the package on Nuget.
Thanks,
Mark
In the process of updating the SignalR.RabbitMq package I also updated EasyNetQ to the latest version (0.14.4.126) and got some problems. Having a look at the SignalR.RabbitMq source it seems that the EasyNetQ commit https://github.com/mikehadlow/EasyNetQ/commit/b99f275f256cbae664457d4da429181d55960604 removed many of the Queue.... static methods, eg DeclareTransient
The latest version of EasyNetQ that works is 0.11.1.113, the SignalR.RabbitMq dependencies should probably be updated.