-
The scripts cannot be completely replaced by ARM yet. At least, I don't think that it can be.
The templates to use are here:
https://github.com/mspnp/iot-journey/tree/bennage/using-arm/setup/LongTermS…
-
With a slow handler that has a large queue the Azure Service Bus prefetch cache fetches an inappropriately large number of messages. This results in the peeklock timing out before the message is hand…
-
http://msdn.microsoft.com/en-us/library/jj673148.aspx
-
Related to: particular/NServiceBus#1929
- Use the native deadlettering capabilities for handling poison messages
- Use DeadLetter forwarding to forward poison messages to the configured "Error" queue
…
-
Currently we do not set any of the strongly typed properties on the Brokered Message. It would be nice if things like contenttype, from, to, replyto got set and also if we had some convention such th…
-
Currently all messages use .Net XML Serializer with a byte[]. It would be nice to support the option for regular String based messages when using serializers like JSON / XML so non-NSB can easily des…
-
Hello guys, any plans to roll out transport for event hub?
-
Using Azure Service Bus as a broker between an Android device and on premise NServiceBus... The serialization type is JSON. Android is using the ASB REST API to send the binary payload to the ASB queu…
-
It would also simplify the design
-
Hi,
migrating to new version of Rebus, I've incurred in quite a big problem.
What happens is that if I use LogicalCallContext to track of the correlation-id in NLog across Tasks, it doesn't work.
T…