I investigated the matter shortly last weekend (other things came to take some time) and we have two options:
* Plain assembly redirect (easy and quick, requires users the to know about it) * Use Spring.NET 2.0 *nightly build*, M1 release hasn't for some reason signed dlls so they won't work with current requirements Going for 3.x release a new and shine Spring.NET 2.0 sounds good, but will require users to use "experimental" (though it's solid). What would be the path to take? -Marko On Friday, August 10, 2012 11:11:28 PM UTC+3, Corey wrote: > > One quick update. Ryan was able to get some of the capabilities for > delivery options DeliverBy, and MaxAttempts into the MsmqTransport. With > the caveat that MaxAttempts must be one if used. > > Marko, any progress on your end? > > On Sat, Aug 4, 2012 at 1:05 PM, Marko Lahma <marko...@gmail.com<javascript:> > > wrote: > >> >> >> I'll have a look wrt Spring problems. Hopefully tomorrow (Sunday). Latest >> Common.Logging is always the best option but need to check whether to use >> binding redirects or upgrade to Spring.NET 2.0 M1.. >> >> -Marko >> >> >> On Saturday, August 4, 2012 12:15:47 AM UTC+3, Corey wrote: >>> >>> -The changes for Rhino.Queues sending options have been pulled in. >>> -- Maximum retry count on send failure >>> -- Deliver by, if time is exceeded the message is discarded >>> -Removal of log4net in favor of Common.Logging >>> -Pulled in spelling error. >>> >>> Ryan is looking into whether or not some or all of the sending options >>> will work with the MSMQ transport as well. >>> >>> Spring tests are not passing due to version conflict (I chose 2.1.1) >>> Marko, are you up for this or would a different version be better? >>> >>> We will begin to incorporate these changes into our environment over the >>> next week or two. Provided things are running smooth I will publish to >>> nuget then. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Rhino Tools Dev" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/rhino-tools-dev/-/5-eRWeybbJYJ. >> To post to this group, send email to rhino-t...@googlegroups.com<javascript:> >> . >> To unsubscribe from this group, send email to >> rhino-tools-d...@googlegroups.com <javascript:>. >> For more options, visit this group at >> http://groups.google.com/group/rhino-tools-dev?hl=en. >> > > -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To view this discussion on the web visit https://groups.google.com/d/msg/rhino-tools-dev/-/shcEsaE3g-EJ. To post to this group, send email to rhino-tools-dev@googlegroups.com. To unsubscribe from this group, send email to rhino-tools-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
