DxWorks.ScriptBee.Plugin.Api
2.0.0
Prefix Reserved
dotnet add package DxWorks.ScriptBee.Plugin.Api --version 2.0.0
NuGet\Install-Package DxWorks.ScriptBee.Plugin.Api -Version 2.0.0
<PackageReference Include="DxWorks.ScriptBee.Plugin.Api" Version="2.0.0" />
<PackageVersion Include="DxWorks.ScriptBee.Plugin.Api" Version="2.0.0" />
<PackageReference Include="DxWorks.ScriptBee.Plugin.Api" />
paket add DxWorks.ScriptBee.Plugin.Api --version 2.0.0
#r "nuget: DxWorks.ScriptBee.Plugin.Api, 2.0.0"
#:package DxWorks.ScriptBee.Plugin.Api@2.0.0
#addin nuget:?package=DxWorks.ScriptBee.Plugin.Api&version=2.0.0
#tool nuget:?package=DxWorks.ScriptBee.Plugin.Api&version=2.0.0
DxWorks.ScriptBee.Plugin.Api
This is the API for the ScriptBee plugin. It contains the interfaces and classes that are used by the plugin to communicate with the ScriptBee service.
For entire documentation check ScriptBee Plugin API
Currently, ScriptBee supports the following types of plugins:
- Loader Plugins
- Linker Plugins
- Helper Functions Plugins
- Script Generator Plugins
- Script Runner Plugins
- Bundle Plugins
Every plugin must have a manifest.yaml file in its root directory. More information about the manifest can be found in
the manifest section.
Services
Besides the plugin interfaces, ScriptBee offers a set of services that can be used by plugins via dependency injection.
IHelperFunctionsContainer
The IHelperFunctionsContainer service is used to register helper functions. Helper functions are a way to extend the
functionality of ScriptBee. They can be used to add custom functions that can be used in the scripts directly.
IHelperFunctionsContainer wraps the helper functions and provides a way to access them.
public interface IHelperFunctionsContainer
{
public Dictionary<string, Delegate> GetFunctionsDictionary();
public IEnumerable<IHelperFunctions> GetFunctions();
}
ScriptRunner uses the IHelperFunctionsContainer service to
get the helper functions and add them
to the script engine.
IHelperFunctionsResultService
The IHelperFunctionsResultService service is used to store the results of the helper functions and have a uniform way
to deal with script outputs.
public interface IHelperFunctionsResultService
{
Task UploadResultAsync(string fileName, string type, string content, CancellationToken cancellationToken = default);
Task UploadResultAsync(string fileName, string type, Stream content, CancellationToken cancellationToken = default);
void UploadResult(string fileName, string type, string content);
void UploadResult(string fileName, string type, Stream content);
}
ScriptBee's default helper functions
use the IHelperFunctionsResultService service to upload the results of the
helper functions.
Run Result Types
ScriptBee has a set of predefined result types that can be used by the helper functions to upload the results.
public static class RunResultDefaultTypes
{
public const string ConsoleType = "Console";
public const string FileType = "File";
public const string RunError = "RunError";
}
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Westwind.Utilities (>= 5.2.8.1)
NuGet packages (4)
Showing the top 4 NuGet packages that depend on DxWorks.ScriptBee.Plugin.Api:
| Package | Downloads |
|---|---|
|
DxWorks.ScriptBee.Plugins.Honeydew
Honeydew ScriptBee Loader Plugin |
|
|
DxWorks.ScriptBee.Plugins.InspectorGit
Inspector Git ScriptBee Loader Plugin |
|
|
DxWorks.ScriptBee.Plugins.JiraMiner
Jira Miner ScriptBee Loader Plugin |
|
|
DxWorks.ScriptBee.Plugins.SoftwareAssessment
Software AssessmentScriptBee Linker Plugin |
GitHub repositories
This package is not used by any popular GitHub repositories.
# Version 2.0.0
## Changes
- upgrade to use dotnet 10
- update Westwind.Utilities to 5.2.8.1