Update README files

[calloncampbell]

Need to update the README.md files with appropriate details and how to use this framework.

[sPhinX-LHJ]

Any difference to Topshelf?

[calloncampbell]

Hi @sPhinX-LHJ , at the core I believe both frameworks do the same thing by allowing you to run your service as a console and easily debug. From there I believe both frameworks take on different roles. Our framework is robust, resilient and meant for high performance. We designed it for use at banks, trading companies, telcos and other business markets where we needed highly configurable and resilient services.

I don't have an example yet, but we support basic workers, passive/active workers, delayed workers and more coming later.

We support IoC as shown in the samples and will support .NET Core v3 when it comes out.

Let us know what you're looking for in comparison to TopShelf and we can consider adding it if it makes sense.

Give our framework a try and let us know what you think.

[calloncampbell]

@sPhinX-LHJ , when I look at TopShelf, the first thing I notice is that it takes a Console application and then runs it as a service. We're the opposite. You create a Windows Service project and then we enable you to run it as a console in debug mode. We then extend the service with additional features that you can opt into using if needed. I hope this helps.

[calloncampbell]

@sPhinX-LHJ, we also based our framework on Workers which is thread based. You then create your logic as a worker and our framework will load it up (1 or more threads), manage the workers, shut them down, respawn, etc. This allows you to focus on your business logic in the worker and not the infrastructure code of creating workers, dealing with threading, etc.

I don't believe TopShelf supports the concept of Workers.