Niknak.Services.ServiceCore
1.4.1
See the version list below for details.
dotnet add package Niknak.Services.ServiceCore --version 1.4.1
NuGet\Install-Package Niknak.Services.ServiceCore -Version 1.4.1
<PackageReference Include="Niknak.Services.ServiceCore" Version="1.4.1" />
paket add Niknak.Services.ServiceCore --version 1.4.1
#r "nuget: Niknak.Services.ServiceCore, 1.4.1"
// Install Niknak.Services.ServiceCore as a Cake Addin #addin nuget:?package=Niknak.Services.ServiceCore&version=1.4.1 // Install Niknak.Services.ServiceCore as a Cake Tool #tool nuget:?package=Niknak.Services.ServiceCore&version=1.4.1
Core service logic. Includes code for dealing with MSMQ, task scheduling and WCF communication. Intended to be used in a Windows service application.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET Framework | net45 is compatible. net451 was computed. net452 was computed. net46 was computed. net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
-
.NETFramework 4.5
- No dependencies.
NuGet packages (2)
Showing the top 2 NuGet packages that depend on Niknak.Services.ServiceCore:
Package | Downloads |
---|---|
Niknak.Services.TaskScheduler.UI
Contains UI components for working with the TaskScheduler library, including embedded Web Forms usercontrols and icons. |
|
Niknak.Services.TaskScheduler
Extends the ServiceCore library with a fully featured task scheduling system. Create your own libraries and classes that use the abstract task classes. Designed to run in a Windows service and be controlled by a web front-end (see TaskScheduler.UI library). |
GitHub repositories
This package is not used by any popular GitHub repositories.
Important bug fix! Previously when an End Time was set for an advanced task iterations outside of the time boundary would be generated, causing issues with setting the terminater timer and generally wasting resources. This is now fixed and tested but anything relying on the fact an iteration would run when it shouldn't will possibly have a problem now.