Skip to content
This repository was archived by the owner on Nov 25, 2024. It is now read-only.

Repository files navigation

ExecutionControl

GitHub

Packages table

PackageStatusPipelineNuGet versionDownloads
ChustaSoft.Tools.ExecutionControlBuild StatusNuGetNuget
ChustaSoft.Tools.ExecutionControl.SqlServerBuild StatusNuGetNuget
ChustaSoft.Tools.ExecutionControl.MySqlBuild StatusNuGetNuget

Packages compatibility table

FrameworkSqlServer FromSqlServer LatestMySql/MariaDb FromMySql/MariaDb Latest
.Net Core 2.11.0.0✔️
.Net Core 2.21.0.01.3.0 (Main pck)
.Net Core 3.01.0.01.3.0 (Main pck)
.Net Core 3.11.0.0✔️1.0.0✔️
.Net 5.01.0.0✔️1.0.0✔️
.Net 6.01.1.0✔️1.1.0✔️

Description:

Tool for define and control backend processes. ExecutionControl allow an application to manage processes by defining using an Enum Type.

Getting started:

  1. Install the required package depending on you infrastructure (MySql or SqlServer)

    • Install-Package ChustaSoft.Tools.ExecutionControl.SqlServer or Install-Package ChustaSoft.Tools.ExecutionControl.MySql
    • dotnet add package ChustaSoft.Tools.ExecutionControl.SqlServer or dotnet add package ChustaSoft.Tools.ExecutionControl.MySql
    • paket add ChustaSoft.Tools.ExecutionControl.SqlServer or paket add ChustaSoft.Tools.ExecutionControl.MySql
  2. Define Enum Type. Enum members must correspond to an specific process inside the solution

    Example: public enum TestDefinedProcesses { [Description("Execution Process 1")] Process1, [Description("Execution Process 2")] Process2, [Description("Execution Process 3")] Process3 }

    At this step, define enum members is mandatory, but not the Description. If Description attribute is added, ExecutionControl will generate the different ProcessDefinition with a custom description in DB, otherwise, the Description will be the same than the name.

  3. Configure NuGet on Startup:

    · On ConfigureServices method:

    services.RegisterExecutionControl(Configuration.GetConnectionString("Connection"));

    a) The configuration requires to specify the Enum type (TestDefinedProcesses in the example above) b) As main parameter, the built-in connection string is mandatory, the tool will generate automatically de DB Schema if you add the configuration step on Configuration Startup method c) By default, the tool specifies 60 minutes to abort a process, to specify a different value, it is possible to add it as second parameter (10 minutes in the example below): services.RegisterExecutionControl(Configuration.GetConnectionString("Connection"), 10);

    · On Configure method:

    app.ConfigureExecutionControl(serviceProvider);

    a) As mentioned on previous point, section b, this line will automatically deploy de DB Schema on the selected database, and also will load the Process Definitions depending on the Enum type

  4. Inside the service, to manage the execution, the following steps are needed:

    a. Inject IExecutionService on constructor, in the example below, we are using Guid type as PK (recommended) private readonly IExecutionService<Guid, TestDefinedProcesses> executionService;

    b. Call Execute method, specifying the Enum member as the Process name for the executed method, at this point we have two different possibilities, in both cases, the execution management is done by the tool:

     a. Simpliest way:
    - Define the process method:
    public bool TestProcess1Method()
    {
    //Process logic goes there
    return true;
    }
    - Run it using IExecutionService
    executionService.Execute(TestDefinedProcesses.Process1, () => TestProcess1Method());
    b. Having context for adding checkpoint events. - Define the process method:
    public bool TestProcess2Method(ExecutionContext<Guid> executionContext)
    {
    //Process logic goes there
    return true;
    }
    - Run it using IExecutionService
    executionService.Execute(TestDefinedProcesses.Process2, (x) => TestProcess2Method(x));
    - By this, during the execution, the process has the possibility to invoke:
    executionContext.AddCheckpoint("Test checkpoint");
    executionContext.AddEndSummary("Test process finished overall summary");
    c. Defining an always running process:
    - Add this Decorator to the Process Enum type:
    [ProcessDefinition(ProcessType.Background, "Background process description")]
    - Define the process method
    - Run it using IExecutionService, in the example, also with context
    executionService.Execute(ProcessExamplesEnum.BackgroundTestProcess, (ec) => TestAlwaysRunning(ec));
    

Thanks for using and contributing

Thanks for using ChustaSoft ExecutionControl in your project. Feel free to contribute, more info in issues section, ChustaSoft Twitter account or contact us via email

Twitter Follow

About

Tool for define and control backend processes

Topics

Resources

Stars

4 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
GitHub - ChustaSoft/ExecutionControl: Tool for define and control backend processes · GitHub
Skip to content
This repository was archived by the owner on Nov 25, 2024. It is now read-only.

Repository files navigation

ExecutionControl

GitHub

Packages table

PackageStatusPipelineNuGet versionDownloads
ChustaSoft.Tools.ExecutionControlBuild StatusNuGetNuget
ChustaSoft.Tools.ExecutionControl.SqlServerBuild StatusNuGetNuget
ChustaSoft.Tools.ExecutionControl.MySqlBuild StatusNuGetNuget

Packages compatibility table

FrameworkSqlServer FromSqlServer LatestMySql/MariaDb FromMySql/MariaDb Latest
.Net Core 2.11.0.0✔️
.Net Core 2.21.0.01.3.0 (Main pck)
.Net Core 3.01.0.01.3.0 (Main pck)
.Net Core 3.11.0.0✔️1.0.0✔️
.Net 5.01.0.0✔️1.0.0✔️
.Net 6.01.1.0✔️1.1.0✔️

Description:

Tool for define and control backend processes. ExecutionControl allow an application to manage processes by defining using an Enum Type.

Getting started:

  1. Install the required package depending on you infrastructure (MySql or SqlServer)

    • Install-Package ChustaSoft.Tools.ExecutionControl.SqlServer or Install-Package ChustaSoft.Tools.ExecutionControl.MySql
    • dotnet add package ChustaSoft.Tools.ExecutionControl.SqlServer or dotnet add package ChustaSoft.Tools.ExecutionControl.MySql
    • paket add ChustaSoft.Tools.ExecutionControl.SqlServer or paket add ChustaSoft.Tools.ExecutionControl.MySql
  2. Define Enum Type. Enum members must correspond to an specific process inside the solution

    Example: public enum TestDefinedProcesses { [Description("Execution Process 1")] Process1, [Description("Execution Process 2")] Process2, [Description("Execution Process 3")] Process3 }

    At this step, define enum members is mandatory, but not the Description. If Description attribute is added, ExecutionControl will generate the different ProcessDefinition with a custom description in DB, otherwise, the Description will be the same than the name.

  3. Configure NuGet on Startup:

    · On ConfigureServices method:

    services.RegisterExecutionControl(Configuration.GetConnectionString("Connection"));

    a) The configuration requires to specify the Enum type (TestDefinedProcesses in the example above) b) As main parameter, the built-in connection string is mandatory, the tool will generate automatically de DB Schema if you add the configuration step on Configuration Startup method c) By default, the tool specifies 60 minutes to abort a process, to specify a different value, it is possible to add it as second parameter (10 minutes in the example below): services.RegisterExecutionControl(Configuration.GetConnectionString("Connection"), 10);

    · On Configure method:

    app.ConfigureExecutionControl(serviceProvider);

    a) As mentioned on previous point, section b, this line will automatically deploy de DB Schema on the selected database, and also will load the Process Definitions depending on the Enum type

  4. Inside the service, to manage the execution, the following steps are needed:

    a. Inject IExecutionService on constructor, in the example below, we are using Guid type as PK (recommended) private readonly IExecutionService<Guid, TestDefinedProcesses> executionService;

    b. Call Execute method, specifying the Enum member as the Process name for the executed method, at this point we have two different possibilities, in both cases, the execution management is done by the tool:

     a. Simpliest way:
    - Define the process method:
    public bool TestProcess1Method()
    {
    //Process logic goes there
    return true;
    }
    - Run it using IExecutionService
    executionService.Execute(TestDefinedProcesses.Process1, () => TestProcess1Method());
    b. Having context for adding checkpoint events. - Define the process method:
    public bool TestProcess2Method(ExecutionContext<Guid> executionContext)
    {
    //Process logic goes there
    return true;
    }
    - Run it using IExecutionService
    executionService.Execute(TestDefinedProcesses.Process2, (x) => TestProcess2Method(x));
    - By this, during the execution, the process has the possibility to invoke:
    executionContext.AddCheckpoint("Test checkpoint");
    executionContext.AddEndSummary("Test process finished overall summary");
    c. Defining an always running process:
    - Add this Decorator to the Process Enum type:
    [ProcessDefinition(ProcessType.Background, "Background process description")]
    - Define the process method
    - Run it using IExecutionService, in the example, also with context
    executionService.Execute(ProcessExamplesEnum.BackgroundTestProcess, (ec) => TestAlwaysRunning(ec));
    

Thanks for using and contributing

Thanks for using ChustaSoft ExecutionControl in your project. Feel free to contribute, more info in issues section, ChustaSoft Twitter account or contact us via email

Twitter Follow

About

Tool for define and control backend processes

Topics

Resources

Stars

4 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' GitHub - ChustaSoft/ExecutionControl: Tool for define and control backend processes · GitHub
Skip to content
This repository was archived by the owner on Nov 25, 2024. It is now read-only.

Repository files navigation

ExecutionControl

GitHub

Packages table

PackageStatusPipelineNuGet versionDownloads
ChustaSoft.Tools.ExecutionControlBuild StatusNuGetNuget
ChustaSoft.Tools.ExecutionControl.SqlServerBuild StatusNuGetNuget
ChustaSoft.Tools.ExecutionControl.MySqlBuild StatusNuGetNuget

Packages compatibility table

FrameworkSqlServer FromSqlServer LatestMySql/MariaDb FromMySql/MariaDb Latest
.Net Core 2.11.0.0✔️
.Net Core 2.21.0.01.3.0 (Main pck)
.Net Core 3.01.0.01.3.0 (Main pck)
.Net Core 3.11.0.0✔️1.0.0✔️
.Net 5.01.0.0✔️1.0.0✔️
.Net 6.01.1.0✔️1.1.0✔️

Description:

Tool for define and control backend processes. ExecutionControl allow an application to manage processes by defining using an Enum Type.

Getting started:

  1. Install the required package depending on you infrastructure (MySql or SqlServer)

    • Install-Package ChustaSoft.Tools.ExecutionControl.SqlServer or Install-Package ChustaSoft.Tools.ExecutionControl.MySql
    • dotnet add package ChustaSoft.Tools.ExecutionControl.SqlServer or dotnet add package ChustaSoft.Tools.ExecutionControl.MySql
    • paket add ChustaSoft.Tools.ExecutionControl.SqlServer or paket add ChustaSoft.Tools.ExecutionControl.MySql
  2. Define Enum Type. Enum members must correspond to an specific process inside the solution

    Example: public enum TestDefinedProcesses { [Description("Execution Process 1")] Process1, [Description("Execution Process 2")] Process2, [Description("Execution Process 3")] Process3 }

    At this step, define enum members is mandatory, but not the Description. If Description attribute is added, ExecutionControl will generate the different ProcessDefinition with a custom description in DB, otherwise, the Description will be the same than the name.

  3. Configure NuGet on Startup:

    · On ConfigureServices method:

    services.RegisterExecutionControl(Configuration.GetConnectionString("Connection"));

    a) The configuration requires to specify the Enum type (TestDefinedProcesses in the example above) b) As main parameter, the built-in connection string is mandatory, the tool will generate automatically de DB Schema if you add the configuration step on Configuration Startup method c) By default, the tool specifies 60 minutes to abort a process, to specify a different value, it is possible to add it as second parameter (10 minutes in the example below): services.RegisterExecutionControl(Configuration.GetConnectionString("Connection"), 10);

    · On Configure method:

    app.ConfigureExecutionControl(serviceProvider);

    a) As mentioned on previous point, section b, this line will automatically deploy de DB Schema on the selected database, and also will load the Process Definitions depending on the Enum type

  4. Inside the service, to manage the execution, the following steps are needed:

    a. Inject IExecutionService on constructor, in the example below, we are using Guid type as PK (recommended) private readonly IExecutionService<Guid, TestDefinedProcesses> executionService;

    b. Call Execute method, specifying the Enum member as the Process name for the executed method, at this point we have two different possibilities, in both cases, the execution management is done by the tool:

     a. Simpliest way:
    - Define the process method:
    public bool TestProcess1Method()
    {
    //Process logic goes there
    return true;
    }
    - Run it using IExecutionService
    executionService.Execute(TestDefinedProcesses.Process1, () => TestProcess1Method());
    b. Having context for adding checkpoint events. - Define the process method:
    public bool TestProcess2Method(ExecutionContext<Guid> executionContext)
    {
    //Process logic goes there
    return true;
    }
    - Run it using IExecutionService
    executionService.Execute(TestDefinedProcesses.Process2, (x) => TestProcess2Method(x));
    - By this, during the execution, the process has the possibility to invoke:
    executionContext.AddCheckpoint("Test checkpoint");
    executionContext.AddEndSummary("Test process finished overall summary");
    c. Defining an always running process:
    - Add this Decorator to the Process Enum type:
    [ProcessDefinition(ProcessType.Background, "Background process description")]
    - Define the process method
    - Run it using IExecutionService, in the example, also with context
    executionService.Execute(ProcessExamplesEnum.BackgroundTestProcess, (ec) => TestAlwaysRunning(ec));
    

Thanks for using and contributing

Thanks for using ChustaSoft ExecutionControl in your project. Feel free to contribute, more info in issues section, ChustaSoft Twitter account or contact us via email

Twitter Follow

About

Tool for define and control backend processes

Topics

Resources

Stars

4 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' GitHub - ChustaSoft/ExecutionControl: Tool for define and control backend processes · GitHub
Skip to content
This repository was archived by the owner on Nov 25, 2024. It is now read-only.

Repository files navigation

ExecutionControl

GitHub

Packages table

PackageStatusPipelineNuGet versionDownloads
ChustaSoft.Tools.ExecutionControlBuild StatusNuGetNuget
ChustaSoft.Tools.ExecutionControl.SqlServerBuild StatusNuGetNuget
ChustaSoft.Tools.ExecutionControl.MySqlBuild StatusNuGetNuget

Packages compatibility table

FrameworkSqlServer FromSqlServer LatestMySql/MariaDb FromMySql/MariaDb Latest
.Net Core 2.11.0.0✔️
.Net Core 2.21.0.01.3.0 (Main pck)
.Net Core 3.01.0.01.3.0 (Main pck)
.Net Core 3.11.0.0✔️1.0.0✔️
.Net 5.01.0.0✔️1.0.0✔️
.Net 6.01.1.0✔️1.1.0✔️

Description:

Tool for define and control backend processes. ExecutionControl allow an application to manage processes by defining using an Enum Type.

Getting started:

  1. Install the required package depending on you infrastructure (MySql or SqlServer)

    • Install-Package ChustaSoft.Tools.ExecutionControl.SqlServer or Install-Package ChustaSoft.Tools.ExecutionControl.MySql
    • dotnet add package ChustaSoft.Tools.ExecutionControl.SqlServer or dotnet add package ChustaSoft.Tools.ExecutionControl.MySql
    • paket add ChustaSoft.Tools.ExecutionControl.SqlServer or paket add ChustaSoft.Tools.ExecutionControl.MySql
  2. Define Enum Type. Enum members must correspond to an specific process inside the solution

    Example: public enum TestDefinedProcesses { [Description("Execution Process 1")] Process1, [Description("Execution Process 2")] Process2, [Description("Execution Process 3")] Process3 }

    At this step, define enum members is mandatory, but not the Description. If Description attribute is added, ExecutionControl will generate the different ProcessDefinition with a custom description in DB, otherwise, the Description will be the same than the name.

  3. Configure NuGet on Startup:

    · On ConfigureServices method:

    services.RegisterExecutionControl(Configuration.GetConnectionString("Connection"));

    a) The configuration requires to specify the Enum type (TestDefinedProcesses in the example above) b) As main parameter, the built-in connection string is mandatory, the tool will generate automatically de DB Schema if you add the configuration step on Configuration Startup method c) By default, the tool specifies 60 minutes to abort a process, to specify a different value, it is possible to add it as second parameter (10 minutes in the example below): services.RegisterExecutionControl(Configuration.GetConnectionString("Connection"), 10);

    · On Configure method:

    app.ConfigureExecutionControl(serviceProvider);

    a) As mentioned on previous point, section b, this line will automatically deploy de DB Schema on the selected database, and also will load the Process Definitions depending on the Enum type

  4. Inside the service, to manage the execution, the following steps are needed:

    a. Inject IExecutionService on constructor, in the example below, we are using Guid type as PK (recommended) private readonly IExecutionService<Guid, TestDefinedProcesses> executionService;

    b. Call Execute method, specifying the Enum member as the Process name for the executed method, at this point we have two different possibilities, in both cases, the execution management is done by the tool:

     a. Simpliest way:
    - Define the process method:
    public bool TestProcess1Method()
    {
    //Process logic goes there
    return true;
    }
    - Run it using IExecutionService
    executionService.Execute(TestDefinedProcesses.Process1, () => TestProcess1Method());
    b. Having context for adding checkpoint events. - Define the process method:
    public bool TestProcess2Method(ExecutionContext<Guid> executionContext)
    {
    //Process logic goes there
    return true;
    }
    - Run it using IExecutionService
    executionService.Execute(TestDefinedProcesses.Process2, (x) => TestProcess2Method(x));
    - By this, during the execution, the process has the possibility to invoke:
    executionContext.AddCheckpoint("Test checkpoint");
    executionContext.AddEndSummary("Test process finished overall summary");
    c. Defining an always running process:
    - Add this Decorator to the Process Enum type:
    [ProcessDefinition(ProcessType.Background, "Background process description")]
    - Define the process method
    - Run it using IExecutionService, in the example, also with context
    executionService.Execute(ProcessExamplesEnum.BackgroundTestProcess, (ec) => TestAlwaysRunning(ec));
    

Thanks for using and contributing

Thanks for using ChustaSoft ExecutionControl in your project. Feel free to contribute, more info in issues section, ChustaSoft Twitter account or contact us via email

Twitter Follow

About

Tool for define and control backend processes

Topics

Resources

Stars

4 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + ' GitHub - ChustaSoft/ExecutionControl: Tool for define and control backend processes · GitHub
Skip to content
This repository was archived by the owner on Nov 25, 2024. It is now read-only.

Repository files navigation

ExecutionControl

GitHub

Packages table

PackageStatusPipelineNuGet versionDownloads
ChustaSoft.Tools.ExecutionControlBuild StatusNuGetNuget
ChustaSoft.Tools.ExecutionControl.SqlServerBuild StatusNuGetNuget
ChustaSoft.Tools.ExecutionControl.MySqlBuild StatusNuGetNuget

Packages compatibility table

FrameworkSqlServer FromSqlServer LatestMySql/MariaDb FromMySql/MariaDb Latest
.Net Core 2.11.0.0✔️
.Net Core 2.21.0.01.3.0 (Main pck)
.Net Core 3.01.0.01.3.0 (Main pck)
.Net Core 3.11.0.0✔️1.0.0✔️
.Net 5.01.0.0✔️1.0.0✔️
.Net 6.01.1.0✔️1.1.0✔️

Description:

Tool for define and control backend processes. ExecutionControl allow an application to manage processes by defining using an Enum Type.

Getting started:

  1. Install the required package depending on you infrastructure (MySql or SqlServer)

    • Install-Package ChustaSoft.Tools.ExecutionControl.SqlServer or Install-Package ChustaSoft.Tools.ExecutionControl.MySql
    • dotnet add package ChustaSoft.Tools.ExecutionControl.SqlServer or dotnet add package ChustaSoft.Tools.ExecutionControl.MySql
    • paket add ChustaSoft.Tools.ExecutionControl.SqlServer or paket add ChustaSoft.Tools.ExecutionControl.MySql
  2. Define Enum Type. Enum members must correspond to an specific process inside the solution

    Example: public enum TestDefinedProcesses { [Description("Execution Process 1")] Process1, [Description("Execution Process 2")] Process2, [Description("Execution Process 3")] Process3 }

    At this step, define enum members is mandatory, but not the Description. If Description attribute is added, ExecutionControl will generate the different ProcessDefinition with a custom description in DB, otherwise, the Description will be the same than the name.

  3. Configure NuGet on Startup:

    · On ConfigureServices method:

    services.RegisterExecutionControl(Configuration.GetConnectionString("Connection"));

    a) The configuration requires to specify the Enum type (TestDefinedProcesses in the example above) b) As main parameter, the built-in connection string is mandatory, the tool will generate automatically de DB Schema if you add the configuration step on Configuration Startup method c) By default, the tool specifies 60 minutes to abort a process, to specify a different value, it is possible to add it as second parameter (10 minutes in the example below): services.RegisterExecutionControl(Configuration.GetConnectionString("Connection"), 10);

    · On Configure method:

    app.ConfigureExecutionControl(serviceProvider);

    a) As mentioned on previous point, section b, this line will automatically deploy de DB Schema on the selected database, and also will load the Process Definitions depending on the Enum type

  4. Inside the service, to manage the execution, the following steps are needed:

    a. Inject IExecutionService on constructor, in the example below, we are using Guid type as PK (recommended) private readonly IExecutionService<Guid, TestDefinedProcesses> executionService;

    b. Call Execute method, specifying the Enum member as the Process name for the executed method, at this point we have two different possibilities, in both cases, the execution management is done by the tool:

     a. Simpliest way:
    - Define the process method:
    public bool TestProcess1Method()
    {
    //Process logic goes there
    return true;
    }
    - Run it using IExecutionService
    executionService.Execute(TestDefinedProcesses.Process1, () => TestProcess1Method());
    b. Having context for adding checkpoint events. - Define the process method:
    public bool TestProcess2Method(ExecutionContext<Guid> executionContext)
    {
    //Process logic goes there
    return true;
    }
    - Run it using IExecutionService
    executionService.Execute(TestDefinedProcesses.Process2, (x) => TestProcess2Method(x));
    - By this, during the execution, the process has the possibility to invoke:
    executionContext.AddCheckpoint("Test checkpoint");
    executionContext.AddEndSummary("Test process finished overall summary");
    c. Defining an always running process:
    - Add this Decorator to the Process Enum type:
    [ProcessDefinition(ProcessType.Background, "Background process description")]
    - Define the process method
    - Run it using IExecutionService, in the example, also with context
    executionService.Execute(ProcessExamplesEnum.BackgroundTestProcess, (ec) => TestAlwaysRunning(ec));
    

Thanks for using and contributing

Thanks for using ChustaSoft ExecutionControl in your project. Feel free to contribute, more info in issues section, ChustaSoft Twitter account or contact us via email

Twitter Follow

About

Tool for define and control backend processes

Topics

Resources

Stars

4 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' GitHub - ChustaSoft/ExecutionControl: Tool for define and control backend processes · GitHub
Skip to content
This repository was archived by the owner on Nov 25, 2024. It is now read-only.

Repository files navigation

ExecutionControl

GitHub

Packages table

PackageStatusPipelineNuGet versionDownloads
ChustaSoft.Tools.ExecutionControlBuild StatusNuGetNuget
ChustaSoft.Tools.ExecutionControl.SqlServerBuild StatusNuGetNuget
ChustaSoft.Tools.ExecutionControl.MySqlBuild StatusNuGetNuget

Packages compatibility table

FrameworkSqlServer FromSqlServer LatestMySql/MariaDb FromMySql/MariaDb Latest
.Net Core 2.11.0.0✔️
.Net Core 2.21.0.01.3.0 (Main pck)
.Net Core 3.01.0.01.3.0 (Main pck)
.Net Core 3.11.0.0✔️1.0.0✔️
.Net 5.01.0.0✔️1.0.0✔️
.Net 6.01.1.0✔️1.1.0✔️

Description:

Tool for define and control backend processes. ExecutionControl allow an application to manage processes by defining using an Enum Type.

Getting started:

  1. Install the required package depending on you infrastructure (MySql or SqlServer)

    • Install-Package ChustaSoft.Tools.ExecutionControl.SqlServer or Install-Package ChustaSoft.Tools.ExecutionControl.MySql
    • dotnet add package ChustaSoft.Tools.ExecutionControl.SqlServer or dotnet add package ChustaSoft.Tools.ExecutionControl.MySql
    • paket add ChustaSoft.Tools.ExecutionControl.SqlServer or paket add ChustaSoft.Tools.ExecutionControl.MySql
  2. Define Enum Type. Enum members must correspond to an specific process inside the solution

    Example: public enum TestDefinedProcesses { [Description("Execution Process 1")] Process1, [Description("Execution Process 2")] Process2, [Description("Execution Process 3")] Process3 }

    At this step, define enum members is mandatory, but not the Description. If Description attribute is added, ExecutionControl will generate the different ProcessDefinition with a custom description in DB, otherwise, the Description will be the same than the name.

  3. Configure NuGet on Startup:

    · On ConfigureServices method:

    services.RegisterExecutionControl(Configuration.GetConnectionString("Connection"));

    a) The configuration requires to specify the Enum type (TestDefinedProcesses in the example above) b) As main parameter, the built-in connection string is mandatory, the tool will generate automatically de DB Schema if you add the configuration step on Configuration Startup method c) By default, the tool specifies 60 minutes to abort a process, to specify a different value, it is possible to add it as second parameter (10 minutes in the example below): services.RegisterExecutionControl(Configuration.GetConnectionString("Connection"), 10);

    · On Configure method:

    app.ConfigureExecutionControl(serviceProvider);

    a) As mentioned on previous point, section b, this line will automatically deploy de DB Schema on the selected database, and also will load the Process Definitions depending on the Enum type

  4. Inside the service, to manage the execution, the following steps are needed:

    a. Inject IExecutionService on constructor, in the example below, we are using Guid type as PK (recommended) private readonly IExecutionService<Guid, TestDefinedProcesses> executionService;

    b. Call Execute method, specifying the Enum member as the Process name for the executed method, at this point we have two different possibilities, in both cases, the execution management is done by the tool:

     a. Simpliest way:
    - Define the process method:
    public bool TestProcess1Method()
    {
    //Process logic goes there
    return true;
    }
    - Run it using IExecutionService
    executionService.Execute(TestDefinedProcesses.Process1, () => TestProcess1Method());
    b. Having context for adding checkpoint events. - Define the process method:
    public bool TestProcess2Method(ExecutionContext<Guid> executionContext)
    {
    //Process logic goes there
    return true;
    }
    - Run it using IExecutionService
    executionService.Execute(TestDefinedProcesses.Process2, (x) => TestProcess2Method(x));
    - By this, during the execution, the process has the possibility to invoke:
    executionContext.AddCheckpoint("Test checkpoint");
    executionContext.AddEndSummary("Test process finished overall summary");
    c. Defining an always running process:
    - Add this Decorator to the Process Enum type:
    [ProcessDefinition(ProcessType.Background, "Background process description")]
    - Define the process method
    - Run it using IExecutionService, in the example, also with context
    executionService.Execute(ProcessExamplesEnum.BackgroundTestProcess, (ec) => TestAlwaysRunning(ec));
    

Thanks for using and contributing

Thanks for using ChustaSoft ExecutionControl in your project. Feel free to contribute, more info in issues section, ChustaSoft Twitter account or contact us via email

Twitter Follow

About

Tool for define and control backend processes

Topics

Resources

Stars

4 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' GitHub - ChustaSoft/ExecutionControl: Tool for define and control backend processes · GitHub
Skip to content
This repository was archived by the owner on Nov 25, 2024. It is now read-only.

Repository files navigation

ExecutionControl

GitHub

Packages table

PackageStatusPipelineNuGet versionDownloads
ChustaSoft.Tools.ExecutionControlBuild StatusNuGetNuget
ChustaSoft.Tools.ExecutionControl.SqlServerBuild StatusNuGetNuget
ChustaSoft.Tools.ExecutionControl.MySqlBuild StatusNuGetNuget

Packages compatibility table

FrameworkSqlServer FromSqlServer LatestMySql/MariaDb FromMySql/MariaDb Latest
.Net Core 2.11.0.0✔️
.Net Core 2.21.0.01.3.0 (Main pck)
.Net Core 3.01.0.01.3.0 (Main pck)
.Net Core 3.11.0.0✔️1.0.0✔️
.Net 5.01.0.0✔️1.0.0✔️
.Net 6.01.1.0✔️1.1.0✔️

Description:

Tool for define and control backend processes. ExecutionControl allow an application to manage processes by defining using an Enum Type.

Getting started:

  1. Install the required package depending on you infrastructure (MySql or SqlServer)

    • Install-Package ChustaSoft.Tools.ExecutionControl.SqlServer or Install-Package ChustaSoft.Tools.ExecutionControl.MySql
    • dotnet add package ChustaSoft.Tools.ExecutionControl.SqlServer or dotnet add package ChustaSoft.Tools.ExecutionControl.MySql
    • paket add ChustaSoft.Tools.ExecutionControl.SqlServer or paket add ChustaSoft.Tools.ExecutionControl.MySql
  2. Define Enum Type. Enum members must correspond to an specific process inside the solution

    Example: public enum TestDefinedProcesses { [Description("Execution Process 1")] Process1, [Description("Execution Process 2")] Process2, [Description("Execution Process 3")] Process3 }

    At this step, define enum members is mandatory, but not the Description. If Description attribute is added, ExecutionControl will generate the different ProcessDefinition with a custom description in DB, otherwise, the Description will be the same than the name.

  3. Configure NuGet on Startup:

    · On ConfigureServices method:

    services.RegisterExecutionControl(Configuration.GetConnectionString("Connection"));

    a) The configuration requires to specify the Enum type (TestDefinedProcesses in the example above) b) As main parameter, the built-in connection string is mandatory, the tool will generate automatically de DB Schema if you add the configuration step on Configuration Startup method c) By default, the tool specifies 60 minutes to abort a process, to specify a different value, it is possible to add it as second parameter (10 minutes in the example below): services.RegisterExecutionControl(Configuration.GetConnectionString("Connection"), 10);

    · On Configure method:

    app.ConfigureExecutionControl(serviceProvider);

    a) As mentioned on previous point, section b, this line will automatically deploy de DB Schema on the selected database, and also will load the Process Definitions depending on the Enum type

  4. Inside the service, to manage the execution, the following steps are needed:

    a. Inject IExecutionService on constructor, in the example below, we are using Guid type as PK (recommended) private readonly IExecutionService<Guid, TestDefinedProcesses> executionService;

    b. Call Execute method, specifying the Enum member as the Process name for the executed method, at this point we have two different possibilities, in both cases, the execution management is done by the tool:

     a. Simpliest way:
    - Define the process method:
    public bool TestProcess1Method()
    {
    //Process logic goes there
    return true;
    }
    - Run it using IExecutionService
    executionService.Execute(TestDefinedProcesses.Process1, () => TestProcess1Method());
    b. Having context for adding checkpoint events. - Define the process method:
    public bool TestProcess2Method(ExecutionContext<Guid> executionContext)
    {
    //Process logic goes there
    return true;
    }
    - Run it using IExecutionService
    executionService.Execute(TestDefinedProcesses.Process2, (x) => TestProcess2Method(x));
    - By this, during the execution, the process has the possibility to invoke:
    executionContext.AddCheckpoint("Test checkpoint");
    executionContext.AddEndSummary("Test process finished overall summary");
    c. Defining an always running process:
    - Add this Decorator to the Process Enum type:
    [ProcessDefinition(ProcessType.Background, "Background process description")]
    - Define the process method
    - Run it using IExecutionService, in the example, also with context
    executionService.Execute(ProcessExamplesEnum.BackgroundTestProcess, (ec) => TestAlwaysRunning(ec));
    

Thanks for using and contributing

Thanks for using ChustaSoft ExecutionControl in your project. Feel free to contribute, more info in issues section, ChustaSoft Twitter account or contact us via email

Twitter Follow

About

Tool for define and control backend processes

Topics

Resources

Stars

4 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })(); GitHub - ChustaSoft/ExecutionControl: Tool for define and control backend processes · GitHub
Skip to content
This repository was archived by the owner on Nov 25, 2024. It is now read-only.

Repository files navigation

ExecutionControl

GitHub

Packages table

PackageStatusPipelineNuGet versionDownloads
ChustaSoft.Tools.ExecutionControlBuild StatusNuGetNuget
ChustaSoft.Tools.ExecutionControl.SqlServerBuild StatusNuGetNuget
ChustaSoft.Tools.ExecutionControl.MySqlBuild StatusNuGetNuget

Packages compatibility table

FrameworkSqlServer FromSqlServer LatestMySql/MariaDb FromMySql/MariaDb Latest
.Net Core 2.11.0.0✔️
.Net Core 2.21.0.01.3.0 (Main pck)
.Net Core 3.01.0.01.3.0 (Main pck)
.Net Core 3.11.0.0✔️1.0.0✔️
.Net 5.01.0.0✔️1.0.0✔️
.Net 6.01.1.0✔️1.1.0✔️

Description:

Tool for define and control backend processes. ExecutionControl allow an application to manage processes by defining using an Enum Type.

Getting started:

  1. Install the required package depending on you infrastructure (MySql or SqlServer)

    • Install-Package ChustaSoft.Tools.ExecutionControl.SqlServer or Install-Package ChustaSoft.Tools.ExecutionControl.MySql
    • dotnet add package ChustaSoft.Tools.ExecutionControl.SqlServer or dotnet add package ChustaSoft.Tools.ExecutionControl.MySql
    • paket add ChustaSoft.Tools.ExecutionControl.SqlServer or paket add ChustaSoft.Tools.ExecutionControl.MySql
  2. Define Enum Type. Enum members must correspond to an specific process inside the solution

    Example: public enum TestDefinedProcesses { [Description("Execution Process 1")] Process1, [Description("Execution Process 2")] Process2, [Description("Execution Process 3")] Process3 }

    At this step, define enum members is mandatory, but not the Description. If Description attribute is added, ExecutionControl will generate the different ProcessDefinition with a custom description in DB, otherwise, the Description will be the same than the name.

  3. Configure NuGet on Startup:

    · On ConfigureServices method:

    services.RegisterExecutionControl(Configuration.GetConnectionString("Connection"));

    a) The configuration requires to specify the Enum type (TestDefinedProcesses in the example above) b) As main parameter, the built-in connection string is mandatory, the tool will generate automatically de DB Schema if you add the configuration step on Configuration Startup method c) By default, the tool specifies 60 minutes to abort a process, to specify a different value, it is possible to add it as second parameter (10 minutes in the example below): services.RegisterExecutionControl(Configuration.GetConnectionString("Connection"), 10);

    · On Configure method:

    app.ConfigureExecutionControl(serviceProvider);

    a) As mentioned on previous point, section b, this line will automatically deploy de DB Schema on the selected database, and also will load the Process Definitions depending on the Enum type

  4. Inside the service, to manage the execution, the following steps are needed:

    a. Inject IExecutionService on constructor, in the example below, we are using Guid type as PK (recommended) private readonly IExecutionService<Guid, TestDefinedProcesses> executionService;

    b. Call Execute method, specifying the Enum member as the Process name for the executed method, at this point we have two different possibilities, in both cases, the execution management is done by the tool:

     a. Simpliest way:
    - Define the process method:
    public bool TestProcess1Method()
    {
    //Process logic goes there
    return true;
    }
    - Run it using IExecutionService
    executionService.Execute(TestDefinedProcesses.Process1, () => TestProcess1Method());
    b. Having context for adding checkpoint events. - Define the process method:
    public bool TestProcess2Method(ExecutionContext<Guid> executionContext)
    {
    //Process logic goes there
    return true;
    }
    - Run it using IExecutionService
    executionService.Execute(TestDefinedProcesses.Process2, (x) => TestProcess2Method(x));
    - By this, during the execution, the process has the possibility to invoke:
    executionContext.AddCheckpoint("Test checkpoint");
    executionContext.AddEndSummary("Test process finished overall summary");
    c. Defining an always running process:
    - Add this Decorator to the Process Enum type:
    [ProcessDefinition(ProcessType.Background, "Background process description")]
    - Define the process method
    - Run it using IExecutionService, in the example, also with context
    executionService.Execute(ProcessExamplesEnum.BackgroundTestProcess, (ec) => TestAlwaysRunning(ec));
    

Thanks for using and contributing

Thanks for using ChustaSoft ExecutionControl in your project. Feel free to contribute, more info in issues section, ChustaSoft Twitter account or contact us via email

Twitter Follow

About

Tool for define and control backend processes

Topics

Resources

Stars

4 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages