You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your improvement related to a problem? Please describe.
As noted in the documentation when BridgeEndpoint configuration names don't match actual EndpointConfiguration names the bridge throws an exception because it can't find the endpoint.
There seem to be common scenarios (MSMQ mentioned in the previous issue) where the casing is for some reason different than what's configured at the endpoint.
A suggestion was made stating that it may be possible to configure case-insensitivity on BridgeEndpoints. This issue is formalizing that suggestion.
Describe the suggested solution
Add an option when to [BridgeEndpoint](https://github.com/Particular/NServiceBus.MessagingBridge/blob/master/src/NServiceBus.MessagingBridge/Configuration/BridgeEndpoint.cs) to AllowCaseInsensitveEndpointNameMatching
Describe alternatives you've considered
Alternately investigate why this issue seems to happen with some MSMQ endpoints and open an issue if there is a bug.
Additional Context
Sender application uses MSMQ transport, NSB version 4.7.12 with .net framework 4.6.
The receiver service in this scenario uses RabbitMQ transport, NSB version 8.0.5 with .Net 6.
The NSB Messaging Bridge uses .net framework 4.8 (to accommodate MSMQ) and the following packages and versions:
NSB version 8.0.5
NSB.MessagingBridge version 2.1.0
NServiceBus.RabbitMQ version 8.0.3
NServiceBus.Transport.Msmq version 2.0.1
The text was updated successfully, but these errors were encountered:
Describe the suggested improvement
Is your improvement related to a problem? Please describe.
As noted in the documentation when BridgeEndpoint configuration names don't match actual EndpointConfiguration names the bridge throws an exception because it can't find the endpoint.
There seem to be common scenarios (MSMQ mentioned in the previous issue) where the casing is for some reason different than what's configured at the endpoint.
A suggestion was made stating that it may be possible to configure case-insensitivity on BridgeEndpoints. This issue is formalizing that suggestion.
Describe the suggested solution
Add an option when to
[BridgeEndpoint](https://github.com/Particular/NServiceBus.MessagingBridge/blob/master/src/NServiceBus.MessagingBridge/Configuration/BridgeEndpoint.cs)
toAllowCaseInsensitveEndpointNameMatching
Describe alternatives you've considered
Alternately investigate why this issue seems to happen with some MSMQ endpoints and open an issue if there is a bug.
Additional Context
Sender application uses MSMQ transport, NSB version 4.7.12 with .net framework 4.6.
The receiver service in this scenario uses RabbitMQ transport, NSB version 8.0.5 with .Net 6.
The NSB Messaging Bridge uses .net framework 4.8 (to accommodate MSMQ) and the following packages and versions:
NSB version 8.0.5
NSB.MessagingBridge version 2.1.0
NServiceBus.RabbitMQ version 8.0.3
NServiceBus.Transport.Msmq version 2.0.1
The text was updated successfully, but these errors were encountered: