Add the ability to run the MassTransit Connector as a Windows Service

[hazel-bohon]

Describe the feature.

Is your feature related to a problem? Please describe.

Not all organizations use containerization for deployment. Requiring them to do so to run the MassTransit Connector represents a barrier to adoption, as these organizations may lack the resources to maintain the necessary infrastructure for containers.

Describe the requested feature

Create and document deployment options that do not require the use of a container.

Describe alternatives you've considered

N/A

Additional Context

If you are reading this issue and are interested in running the MassTransit Connector outside of containerization environments. What would your preferred deployment process be?

[JonTheTurnip]

This is currently a blocker for us, it'd be really great to get this feature actioned so that we can start using ServicePulse with MassTransit.

[ramonsmits]

@JonTheTurnip as a workaround you can clone this repo and build it.

The project https://github.com/Particular/ServiceControl.Connector.MassTransit/tree/master/src/ServiceControl.Connector.MassTransit.Host is the exact same entry point as the container and all guidance around environment variables is also the same.

1. Can you share details on your dev and prod environments? Is this Windows, OSX, Linux?
2. What are your hosting requirements? ServicePulse for example is installable as a Windows Service. Is that what you want?

[JonTheTurnip]

@ramonsmits thank you for the suggestion, not sure why that didn't occur to me to start with!

To answer your questions:

1. Windows for all environments
2. Service Pulse hosted as windows service sounds ideal

Sounds like there are no longer any barriers to me trying out Service Pulse in a dev environment. I'll report back within a few weeks if I encounter and issues. Thanks again!

[ramonsmits]

@JonTheTurnip Based on your feedback I'll adjust the title to reflect that you would want to run it as a windows service.