Geek Answers Handbook

Updating NServiceBus from 2.5 to 3.2 always restores MSMQ, is there any way to stop this?

I am currently working on updating our application to use the NServiceBus 3.2, not the 2.5 that we used. The problem is that when I start the service with a link to 3.2, it has a problem with creating performance counters, which led me to run RunMeFirst.bat to create counters.

Once this is done, the service works as expected, but the problem is that RunMeFirst.bat always reinstalls MSMQ in our environment, which in turn removes all existing queues / messages. This is not really an option for us in a production environment, so you can do this by installing performance counters, but without reinstalling MSMQ, is this possible?

+4
source share
1 answer

The recommendation is only to call RunMeFirst.bat on fresh machines to avoid the problem you mention. At the same time, we plan to improve our infrastructure installers in this regard:

https://github.com/NServiceBus/NServiceBus/issues/651

+1
source

More articles:


All Articles