Migration of Traditional Windows Service to Service Fabric

I'm kicking the tires on the preview release of Service Fabric for Windows Servers found here: Create and manage a cluster running on Windows Server

We are trying to solve the problem of the perception of too many Windows services to manually manage, contemplating infrastructures that would make the services more automatically managed. We currently run on-premises, so we are looking at Service Fabric for Windows Servers, not Service Fabric on Azure.

I have a native Windows service (Windows NT Service) compiled in Embarcadero C++ Builder XE7 that currently /install and /uninstall's itself into the Windows Service Control Manager. The service binds to a port using a WebBroker to receive HTTP requests. Data is currently being retrieved from an Oracle database. It is small in scope, but in my opinion not advanced enough to call a microservice.

These particular services do not run with a console. They run via a WinMain() method instead of a main(). We do utilize a command-line parameter to pop up a form that runs the service process for easy debugging in development, but this does not block if run on the console.

What would be involved in getting this application up and running as a guest executable? Does the project need to be recompiled as a console application to run within service fabric? Any other gotcha's you foresee?

I understand that this is a preview release, so I commit to doing the research to get the answer updated if there are discrepancies with the info in the RTM.

• Start here for Guest executables. Any executable will do, no console is needed.
• Listening for incoming traffic requires ports to be mapped in the ServiceManifest file.
• Running with elevated privileges is explained here.
• Make sure your executable doesn't require user interaction at the console level.