We've been using topshelf 2.3 on a project now for a couple of months that takes advantage of the shelving feature. All in all topshelf has been great, and it's really simplified our service setup process. We're also using MassTransit with great success. So, first of all, THANKS for all the things that you're doing to contribute to the open source community!We've run into an issue with one of our shelves where it seems to stop working after a few weeks of the service being on. The process is still up and running, it's just that the shelf isn't doing its work (as evidenced by its log files).As you can imagine, this is a difficult one to reproduce b/c it requires a long run time and even then it's intermittent. Has anyone else seen something like this occur with topshelf 2.3 shelves? Now, it's quite possible (shoot - likely with my stuff) that this is in our code, but figured I'd check here first.Follow up question. I see with v3.0 that shelving support has been removed and may/may not be re-introducded. I liked the idea of being able to package multiple independent shelves under a single windows service, which is why we pulled in topshelf initially. Given the current project direction, would your recommendation be that people use one service per process, or is there some other mechanism (bottles?) wherein you see the shelving type approach being viable going forward?Thanks!