Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include Default Pre-Built Runners as Executable #23

Open
michaelschnyder opened this issue Apr 13, 2017 · 0 comments
Open

Include Default Pre-Built Runners as Executable #23

michaelschnyder opened this issue Apr 13, 2017 · 0 comments

Comments

@michaelschnyder
Copy link
Member

michaelschnyder commented Apr 13, 2017

Forked Execution always requires you to create an additional console application that hosts the runtime and the communication client to the fex-endpoint.

Suggestion: Include pre-built executables so that no additional project is needed. This "Default" Runners would need to be extracted on start and would load all required Assemblies on load

Adjustments
Extend the configuration so that an external or "internal" runner can be specified.

var config = new ForkedExecutionConfiguration()
{
    // External Runner
    JobRunnerExecutable = new ExternalRunner("Jobbr.Server.ForkedExecution.TestEcho.exe"),

    // Default Runner
    JobRunnerExecutable = new DefaultRunner(),
};

Since the runner is pre-build, we need to make sure that

  • It is compatible with the target Framework Version of the Jobs Assembly (i.e. 32bit, 64bit, version)
  • Supports a DI for Jobs
  • Supports configuration of Logging Libs?
  • Provide an additional app.config.
  • Make sure the required assemblies are loaded automatically
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant