Found 12 packages
Manage Dynamics 365 processes (workflows, actions, BPF, cloud flows) in bulk: load from a solution, filter/search, activate or deactivate multiple items, and export the list to CSV.
Asp.Net MVC Grid with Ajax CRUD opeartions and also supports Search, Change Page size and Paging. User can add toggle buttons like Activate/Deactivate with jQuery Modal Popup in rows
A small tool to help CI system activate and deactivate Xamarin licenses.
The jQuery BlockUI Plugin lets you simulate synchronous behavior when using AJAX, without locking the browser.
Eziriz IntelliLock Licensing - Needed for custom licensing of an application or control https://www.eziriz.com/intellilock_online_help/source/license_agreement.html - This Library enables you to: * check the detailed license status * deactivate and reactivate license files (via license server or reactivation code) * direcly load license files * generate Hardware IDs * define your own dialog box using the IntelliLock.DialogBoxAttribute attribute * prevent types and members from obfuscation using the IntelliLock.ObfuscationAttribute attribute - The functionality of this library is only available AFTER IntelliLock processed your assembly. And after IntelliLock processed your assembly IntelliLock.Licensing.dll is not needed anymore. Therefore you can ship your software without this library.
XrmToolBox plugin that lets you bulk activate, deactivate, or reassign ownership of Power Automate cloud flows within Dynamics 365 solutions. Easily select a solution, review all included flows, and apply changes to multiple flows at once with real-time status updates.
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.
Asp.Net MVC Grid with Ajax Paging. It also supports to search and change pagesize. It has got Edit, Delete, Activate and Deactivate features with jQuery Modal Popup
C# Source Generators for use with the Godot Game Engine (supports Godot 4 and .NET 9!) * `SceneTree` class attribute: -- Generates class property for uniquely named nodes -- Provides strongly typed access to the scene hierarchy (via `_` operator) -- NEW: TscnFilePath for static access to tscn file * `GodotOverride` method attribute: -- Allows use of On*, instead of virtual _* overrides -- (Requires partial method declaration for use with Godot 4) * `Notify` property attribute: -- Generates boiler plate code, triggering only when values differ -- (Automagically triggers nested changes for Resource and Resource[]) * `InputMap` class attribute: -- Provides strongly typed access to input actions defined in godot.project -- NEW: Attribute option to replace StringName with your own custom object/handler * `LayerNames` class attribute: -- Provide strongly typed access to layer names defined in godot.project * NEW: `Autoload`/`AutoloadRename` class attribute: -- Provide strongly typed access to autoload nodes defined in godot.project * `CodeComments` class attribute: -- Provides a nested static class to access property comments from code (useful for in-game tooltips, etc) * `OnInstantiate` method attribute: -- Generates a static Instantiate method with matching args that calls attributed method as part of the instantiation process -- (Also generates a protected constructor to ensure proper initialisation - can be deactivated via attribute) * `OnImport` method attribute (GD4 only): -- Generates default plugin overrides and options to make plugin class cleaner (inherit from OnImportEditorPlugin) * Includes base classes/helpers to create project specific source generators
This NuGet package is an all-in-one utility library designed to streamline development for Microsoft Dynamics 365 (CRM). It provides a rich set of reusable functions and abstractions that simplify complex and repetitive tasks across the Dynamics platform. Key features include: CRUD Operations: Simplified methods for creating, retrieving, updating, and deleting records across all standard and custom entities. Workflow Control: Easily activate, deactivate, and trigger on-demand workflows. Security Management: Retrieve and manage security roles and user-role assignments. Metadata Access: Fetch option set values, lookup configurations, and entity metadata. Utility Methods: Helper functions for working with EntityReference, QueryExpression, FetchXML, and more. Error Handling: Consistent exception wrapping and logging support for easier debugging. Compatibility: Works with both Dynamics 365 Online environments. Whether you're building plugins, custom workflow activities, console apps, or integration tools, this package provides a reliable foundation to accelerate Dynamics CRM development and reduce boilerplate code.
The stating library enables you to use states in an easy or complex way - whatever you like. I decided to separate the transitions between the states from the states themselves, because I thought they should not be part of them. You can extend these StateTransition and have therefore full control over which IState should appear after the deactivated one, but you don't need to. If you have simple one-after-one-transitions, then you just need to specify that at adding the IState object to the StateMachine and that's it. The StateMachine will do the rest for you.
The BlockUI component lets you simulate synchronous behavior when using Blazor, without locking the browser. When activated, it will prevent user activity with the page until it is deactivated. BlockUI adds elements to the DOM to give it both the appearance and behavior of blocking user interaction.