Hi Devindran,
I've just pushed a new sample that might help with your migration. It introduces the concept of a Forwarding Address that can be configured within an endpoint for each message type.
In your scenario you could use this as follows:
Step 1 - move your existing V5 endpoint to a new address. Do not update the routing of any of your other endpoints. They will continue to send messages to the original address.
Step 2 - create a V7 endpoint with a forwarding address for each of the 15 message types. This will forward all incoming messages to your old endpoint.
Step 3 - for each message type being handled, create a handler in your V7 endpoint for that message type and remove the forwarding address for that message type. New messages of this type will now be handled by the V7 instance only. There may be in-flight messages already in the input queue of your old endpoint that will still be handled there.
Step 4 - once all message handlers have been migrated, you can remove the forwarding address infrastructure from your new V7 endpoint
Step 5 - once the input queue for your old endpoint has been completely drained, you can decommission your original endpoint
At the moment the sample is targeting NServiceBus version 6 but I will be updating it version 7 as well before it is fully released.
Regards,
Mike Minutillo
Particular Software