This component adds support for Clockwork to call as Gears Carbonite ORM operations on top of the MySQL DBMS. Clockwork is a complete programming paradigm that lets you model and execute complex business processes via Gears that encapsulate specific business steps. Then you assemble those Gears together to compose a myriad of business processes called Mechanisms. A Mechanism is by definition a Gear, so you can create new Mechanisms by mixing and matching Mechanisms and Gears in the vast Clockwork library or those you already have for your private use. Clockwork include a large library of ready to use Gears to for example do declarative validations, make other Gears asynchronous, and even bind other KEYSTONE components to the Clockwork paradigm. KEYSTONE is a modern, multi-paradigm, data-centric software development framework. Visit http://www.keystoneframework.com for more details.
A C# lock replacement enabling async-await in between acquire and release. High performance, Re-entrant, with no caveat. Able to re-entrant/re-acquire the same across threads within the same task.
Clockworks is a .NET library for deterministic, fully controllable time in distributed-system simulations and tests. It provides a simulated TimeProvider with deterministic timer scheduling, TimeProvider-driven timeouts, UUIDv7 generation, and Hybrid Logical Clock (HLC) utilities with lightweight instrumentation.
Provides the basis for implementing the Ambient Context pattern. Includes a Clock implementation based on it. The Ambient Context pattern is an Inversion of Control (IoC) pattern that provides static access to a dependency while controlling the dependency from the outside. The pattern optimizes code reachability at the cost of reduced transparency, making it suitable for obvious, ubiquitous, rarely-changing dependencies. For example, an entity's constructor can access Clock.UtcNow, avoiding the need to inject the creation datetime or a dependency, at the cost of hiding the fact that a unit test could control the timestamp from the outside. An example from .NET is System.Transactions.TransactionScope. Any code (such as the database connector) can access the static Transaction.Current, yet outer code in the current execution flow controls it, through TransactionScopes. https://github.com/TheArchitectDev/Architect.AmbientContexts Release notes: 2.0.1: - Updated dependencies to the latest versions and removed some unused dependencies. 2.0.0: - BREAKING: ClockScope no longer has a configurable default scope. (See also next item). - BREAKING: Removed explicit support for "configured default scopes", i.e. scopes configured on startup. They posed too many concurrency risks, such as in test runs. (Default scopes without any configuration are still supported.) - BREAKING: Removed the RemoveAmbientScope() method. Deactivate() should be used instead. - Added support for netstandard2.0. - ClockScope's constructor now prefers UTC datetimes, to avoid lossy conversions (due to DST). - ClockScope now exposes a convenience constructor that takes a DateTime instead of a Func<DateTime>. 1.1.1: - Manually disposing scopes from a deeper async level (such as a DisposeAsync() method with the async keyword) now properly affects methods up the call stack and no longer breaks scope nesting. - Improved the protections against race conditions. - Parent properties are no longer unset on disposal (although implementations should not rely on this detail). - Performance improvement: A scope now avoids even instantiating its AsyncLocal as long as only its default scope is used, as is common in production for certain scopes. - Performance improvement: The JIT can now inline more code, since exceptions have been moved into helper methods. 1.1.0: - Introduced non-generic AmbientScope base class. - Performance improvement: A scope now avoids touching its AsyncLocal as long as only its default scope is used, as is common in production for certain scopes.
Reliable unique ID generation and management for distributed applications. Auto-increment IDs reveal sensitive information. UUIDs (also known as GUIDs) are inefficient as primary keys in a database. Having two different IDs is cumbersome and counterintuitive. We can do better. - For a 93-bit UUID replacement that is efficient as a primary key, use the DistributedId. - For a 128-bit 128-bit UUID replacement with the advantages of the DistributedId and practically no rate limits or collisions, at the cost of more space, use the DistributedId128. - To expose IDs externally in a sensitive environment where zero metadata must be leaked, transform them with PublicIdentities. https://github.com/TheArchitectDev/Architect.Identities Release notes: 2.2.0: - Frameworks: Added net9.0 and net10.0. Removed netcoreapp3.1, net5.0, net6.0, net7.0. - Platforms: (.net8.0+) Now available on 32-bit and big-endian platforms also. 2.1.1: - Enhancement: Upgraded package versions. 2.1.0: - Semi-breaking: IPublicIdentityConverter now features additional methods, although the type is generally not user-implemented. - Semi-breaking: HexadecimalIdEncoder's char-based parameters have been renamed from "bytes" to "chars". - Added DistributedId128, a 128-bit (Guid/UInt128) DistributedId variant with practically no rate limits or collisions that also doubles as a version-7 UUID. - Added encoding methods for UInt128. - Added extension methods to transcode between UInt128 and Guid. - Added public identity conversions for UInt128 and Guid. - DistributedIdGeneratorScope and DistributedId128GeneratorScope now expose the CurrentGenerator property, which helps when implementing generators that need to piggyback on the encapsulated generator. 2.0.0: - BREAKING: Removed Fluid. Ambient scopes with startup configuration are now considered undesirable. - BREAKING: Removed ApplicationInstanceId. Ambient scopes with startup configuration are now considered undesirable. - BREAKING: Removed ambient access to IPublicIdentityConverter. Ambient scopes with startup configuration are now considered undesirable. - BREAKING: IdEncoder has been reworked into BinaryIdEncoder, AphanumericIdEncoder, and HexadecimalIdEncoder. - BREAKING: ID decoding methods now throw if the input is too long. This is specially relevant for strings (such as query parameters) where 0123456789123456 and 0123456789123456aaaa should not produce the same ID. - BREAKING: IPublicIdentityConverter now throws on big-endian architectures, instead of risking silent portability issues between architectures. - BREAKING: Now using AmbientContexts 2.0.0. - Semi-breaking: DistributedIds are now always 28 digits, to avoid a change from 27 to 28 digits in the future. Newly generated IDs will be significantly greater than before. Avoid downgrading after upgrading. - DistributedIds can now burst-generate ~128,000 IDs at once before the ~128 IDs per millisecond throttling kicks in. This makes throttling much less likely to be encountered. - DistributedId now stays incremental even under clock adjustments of up to 1 second. (Note that the UTC clock remains unaffected by DST.) - Hexadecimal ID encodings are now supported. - IPublicIdentityConverter now comes with a TestPublicIdentityConverter implementation for unit tests. - Added UnsupportedOSPlatform("browser") to PublicIdentities, due to continuing lack of AES support. 1.0.2: - Now using AmbientContexts 1.1.1, which fixes extremely rare bugs and improves performance. 1.0.1: - Now using AmbientContexts 1.1.0, for a performance improvement.
Monitor the temperature sensors, fan speeds, voltages, load and clock speeds of your computer.
Helper classes to simulate the flowing of time when using IClock from EMG.Utilities.Clock.Testing
Helper class to avoid accessing statically the current date and time.
The generic repository and unit of work pattern for entity framework
This is updated punchclock nuget that supports Reactive 4.0 There is a problem on Android when compiling System.Threading.Tasks.Extension need to downgrade from 4.5.1 to 4.0.0 Original was not upfated for a while.
Rebex Time is an SNTP/NTP, Time and Daytime client library that enables your application to determine the exact time from Internet time servers. This is a paid commercial product with a free 30-day trial: - Trial mode: Start your free 30-day trial by generating your trial key at https://rebex.net/support/trial-key.aspx - Licensed mode: Purchase the product at https://rebex.net/shop/ and get your full license key at https://rebex.net/protected/nuget When the full license key is provided, NuGet.org repository can be used to retrieve versions of Rebex components covered by your support contract. Supported platforms: - .NET 10 on Windows, Linux, macOS, Android, iOS/tvOS - .NET 9 on Windows, Linux, macOS, Android, iOS/tvOS - .NET 8 on Windows, Linux, macOS, Android, iOS/tvOS - .NET 7 on Windows, Linux, macOS, Android, iOS/tvOS - .NET 6 on Windows, Linux, macOS - .NET 5 on Windows, Linux, macOS - .NET Framework 4.0, 4.5.x, 4.6.x, 4.7.x, 4.8.x - .NET Framework 3.5 SP1 - .NET Core 3.1 on Windows, Linux, macOS - Xamarin.Android (10.1 and higher; via .NET Standard 2.1) - Xamarin.iOS (13.10 and higher; via .NET Standard 2.1) - Mono 6.0 or higher on Linux and macOS
This package provides functionality for communicating with ZKTeco devices. It includes easy methods and built-in attendance models along with other frequently used methods such as CRUD operations for users and Read, Delete. Note: This package is designed for .NET Standard 2.0 and may not work with .NET 7. For other customization like scheduling data retrieval, deletion, and other project integration work, contact: Email: gauravmaharjan000@gmail.com LinkedIn: https://www.linkedin.com/in/gaurav-maharjan-550042215/
It is well known that DateTime.Now is often used inappropriately. For example, it may be used together with TimeSpan to produce a task's timeout point or subtracted from another DateTime to calculate a duration. This can cause subtle bugs because DateTime is not monotonic: the system clock can change, making the result of the subtraction inaccurate -- potentially causing a premature timeout or an infinite loop. Yet, DateTime is an incredibly convenient and widely used value type in .NET code and is especially useful when printed in ISO-8601 format (with the "O" format specifier). With the "O" specifier, you can resolution down to tenths of a microsecond, which is nice. Until you learn that the resolution of the system clock is usually more coarse than several *milliseconds*, making the additional decimal places misleading garbage values. For calculating durations (time between events), it is better to use a high-resolution and monotonic clock like that provided by System.Diagnostics.Stopwatch: on most computers it is far more **accurate** than DateTime.Now even though, seemingly paradoxically, on a few systems, its *resolution* is lower than that of DateTime. Also, unsurprisingly, Stopwatch does not provide values that correlate to times of day: while it is appropriate for calculating durations, it is inappropriate for timestamping against a readable date and time. This library provides timestamps (both as DateTime and as analogous value types it defines) that use the Stopwatch (and your system's high peformance event counter) as its clock, but returns values as DateTimes or an analog thereto so that these values can be used for a mixed purpose of timestamping and providing a meaningful way to calculate time elapsed between events or to calculate how long to perform a programmatic task.
This package provides the functionality to utilize the features of Syncfusion® WinForms TreeMap control and more.
An IClock interface and default implementation SystemClock to make time-based logic testable.
Helper classes to simulate the flowing of time when using IClock from EMG.Utilities.Clock
This component adds support for Clockwork to call System.Net operations as Gears. Clockwork is a complete programming paradigm that lets you model and execute complex business processes via Gears that encapsulate specific business steps. Then you assemble those Gears together to compose a myriad of business processes called Mechanisms. A Mechanism is by definition a Gear, so you can create new Mechanisms by mixing and matching Mechanisms and Gears in the vast Clockwork library or those you already have for your private use. Clockwork include a large library of ready to use Gears to for example do declarative validations, make other Gears asynchronous, and even bind other KEYSTONE components to the Clockwork paradigm. KEYSTONE is a modern, multi-paradigm, data-centric software development framework. Visit http://www.keystoneframework.com for more details.
The CoolClock extension component uses the CoolClock widget (http://randomibis.com/coolclock/) to render amazing analog clocks as Wisej.NET Real Time widgets. Supports several skins, logarithmic scale, and several properties to configure the tick delay or hide the second’s hand.
Package Description
Defines IClock that provides a simple abstraction for unit testing dates and times.
Itc4net is a C# implementation of Interval Tree Clocks, a causality tracking mechanism.
Ds323x I2C family of real time clocks (DS3231, DS3231M, DS3232)
Nuget package of 'Clock' provided by Aiursoft
A C# lock replacement for async/await, supporting recursion/re-entrance and asynchronous waits. Handles async recursion correctly - note that Nito.AsyncEx does not! Also provides an asnyc fiendly global Mutex class AsyncMutexLock.
Bonsai Library containing interfaces for data acquisition and control of Harp ClockSynchronizer devices.
Lightweight async mutual exclusion and bounded concurrency primitives for modern .NET applications.
Implements the clock synchronization extesion as defined by the Neuro-Foundation (neuro-foundation.io).
This is a set of simplest javascript modules that can help to you organize your framework on ASP.NET (MVC). This is just for a begin your js-framework. For example: control DataSource - is loader that can data from web api with pager and it cat make selection.
Clockpicker binding library for Bridge.NET projects.
Stravaig Clock is a way of getting contemporary date and time information in an application that is easy to unit test without the need to rely on tolerances. Built on Thursday, 10 August 2023 at 21:23:39 +00:00. Build run details at: https://github.com/Stravaig-Projects/Stravaig.Clock/actions/runs/5826236894 Release notes at: https://github.com/Stravaig-Projects/Stravaig.Clock/releases/tag/v0.2.0
Stravaig Clock Testing is a set of test fakes for use with Stravaig.Clock. Built on Thursday, 10 August 2023 at 21:23:49 +00:00. Build run details at: https://github.com/Stravaig-Projects/Stravaig.Clock/actions/runs/5826236894 Release notes at: https://github.com/Stravaig-Projects/Stravaig.Clock/releases/tag/v0.2.0