It might be far better is you outline what you are actually trying to achieve so that the best advice can be given.As for for the small amount you have provided the short answer is you can't.
To clear up some terminology to start with a
Service as you describe it must be a ServiceStack Service and that is designed to be used within the the ServiceStack ecosystem, to explain the Jiwa ecosystem the components are as follows
- Jiwa.Exe: A winforms application that loads and uses a number of class libraries for its interface and business logic rules.
- Jiwa Plugin Scheduler Windows Service: A windows service that loads up the plugins and look at any schedules in the database and executes the code in the appropriate scheduled plugins.
- Jiwa Self Hosted Rest API: A Windows Service that sets up the environment to host a ServiceStack Server and then calls the configure function on any REST API plugins to add the functionality to the server.
The first two are not designed nor intended to host a ServiceStack Server or ServiceStack Service,
they also don't have any dependency injection / inversion of control support.
Without knowing what you are trying to achieve, if you want code that operates out of all three applications my advice would be to
take a leaf out of Jiwa's playbook and build a class library that referenced the Jiwa manager and any business object libraries etc you needed and add this as an embedded reference to an appropriate plugin for each application and wrapper calls to your class library as appropriate. Note any class library must be targeted as 32 bit and the 4.7.1 framework.
If you need some sort of singleton version in the Jiwa application then wrapper the library in a static class and initialise anything inside the application plugin like hooking the manager into your library.
This link
https://stackoverflow.com/questions/214 ... e-injected might let you get the container going in the other two applications but like I said a class library might be a simpler choice.