cdmdotnet
NuGet publisher profile
Packages (72)
cdmdotnet.Logging
This logging library makes large use of enterprise correlation. In a lot of applications that incorporate various small and large services, it is often important to correlate events that happen across these services. It gives us a business workflow view of the various events that happen in the application, its components and services. This library provide operation and activity ID management and propagation. The main difference with this library over other is that you can configure each type of log separately. You can enable fatal, error, warning, debugging, informational, progress and sensitive data logging all independently of each other. This is more flexible than the concept of minimum level logging, such as that in log4net or serilog e.g. enabling one warning in this libraries will enable error and fatal logging as well. This library allows you to set those settings independently of each other. The SqlLogger maps AdditionalData to table columns, where the key of the dictionary entry is the column name and the value is serialised to JSON as the column value. MetaData is serialised to a single JSON value stored in the MetaData column. This means you can store data such as a User ID or Job ID in a separate column so you can filter more efficiently with indexes and partitions. TraceLogger and ConsoleLogger both seralise and format all information into a single string. The MultiLogger allows you to configure several different loggers to be used at once with different settings for each logger. Usage is in the form of: static void Main() {   ICorrelationIdHelper correlationIdHelper = new WebCorrelationIdHelper();   // This value will be set automatically to all logs within this thread... so long as System.Threading.Tasks.Task.Factory.StartNew is used.   correlationIdHelper.SetCorrelationId(Guid.NewGuid());   DoSyncWork();   DoAsyncWork(); } static void DoSyncWork() {   ILogger logger = new SqlLogger();   logger.LogDebug("Some technical debugging details."); } static void DoAsyncWork() {   System.Threading.Tasks.Task.Factory.StartNew(() => {     ILogger logger = new ConsoleLogger();     logger.LogInfo("An informative message.");   }); } This package installs cdmdotnet.Logging.dll with includes core logging functionality. Other packages depend on cdmdotnet.Logging for specific implementations.
Cqrs
A lightweight enterprise Function as a service (FaaS) framework to write function based serverless and micro-service applications in hybrid multi-datacentre, on-premise and Azure environments, offering modern patterns such as CQRS and event-sourcing. Offering a superior combination of serverless, micro-service and traditional deployments both in the cloud and on-premise to suit any business. Deployments can be inter-conntected with each other sharing data and resourcing or independant and issolated while providing a consistent framework and guideline for both development, deployment, DevOps and administration. CQRS.NET has been designed with modularity in mind... see the number of technology packages below you can chose from. Modularity applies to both development concerns like storage as well as operational modularity such as serverless or micro-service deployment, PaaS, VMs or container packaging. Every package and design choice made should be interchangeable with custom code if needed.
cdmdotnet.Performance
cdmdotnet.Performance
Chinchilla.Logging
Chinchilla.Logging is a .NET Core port of cdmdotnet.Logging, an abstracted logging platform for .NET. It can help you collect reliable logs for your application regardless of its size or complexity with minimal performance implications. This logging library makes large use of enterprise correlation. In a lot of applications that incorporate various small and large services, it is often important to correlate events that happen across these services. It gives us a business workflow view of the various events that happen in the application, its components and services. This library provide operation and activity ID management and propagation. The main difference with this library over other is that you can configure each type of log separately. You can enable fatal, error, warning, debugging, informational, progress and sensitive data logging all independently of each other. This is more flexible than the concept of minimum level logging, such as that in log4net or serilog e.g. enabling one warning in this libraries will enable error and fatal logging as well. This library allows you to set those settings independently of each other. The SqlLogger maps AdditionalData to table columns, where the key of the dictionary entry is the column name and the value is serialised to JSON as the column value. MetaData is serialised to a single JSON value stored in the MetaData column. This means you can store data such as a User ID or Job ID in a separate column so you can filter more efficiently with indexes and partitions. EventLogger, TraceLogger and ConsoleLogger both seralise and format all information into a single string. The MultiLogger allows you to configure several different loggers to be used at once with different settings for each logger. See https://github.com/cdmdotnet/logging/wiki/Quick-How-To for usage details. This package installs Chinchilla.Logging.dll which includes core logging functionality. Other packages depend on Chinchilla.Logging for specific implementations.
Cqrs.Ninject
Provides preconfigured Ninject modules that will wire up the required component necessary. Several modules are optional such as the InProcess or the SimplaifySQL modules. You only need to use those if you are using InProcess or SQL.
Cqrs.Mongo
Use MongoDB as the read store and data store in CQRS.NET
Cqrs.Modelling
A visual designer for the lightweight CQRS.net framework. Using this package you can generate much of the boiler plate code involved in implementing a scalable, enterprise grade CQRS project ready for deployment on-premise or on Azure.
Manatee.Trello
A fully object-oriented .Net wrapper for the TrelloAPI.
Cqrs.Azure.ConfigurationManager
Use Azure Configuration Manager as the configuration manager in CQRS.NET
Cqrs.Azure.ServiceBus
Use Azure ServiceBus as a message, event or command bus in CQRS.NET
Cqrs.EventStore
Use Greg Young's event store as the Event Store in CQRS.NET
Chinchilla.StateManagement
Chinchilla.StateManagement is a .NET Core port of cdmdotnet.StateManagement, a C# state management framework that provides a consistent abstraction for accessing data from various collections such as thread bound contexts, HTTP Request and Response collections as well as HTTP Cookies.
Cqrs.Ninject.EventStore
Use Ninject as your IoC container of choice with Greg Young's Event Store for CQRS.NET
Cqrs.Azure.DocumentDb
Use Azure Cosmos DB (DocumentDB) as an event store, read store and data store in CQRS.NET
Cqrs.Ninject.Mongo
Use Ninject as your IoC container of choice with MongoDB for CQRS.NET
Cqrs.Ninject.Azure.ServiceBus.CommandBus
Use Ninject as your IoC container of choice when using Microsoft Azure ServiceBus for CQRS.NET as your command bus
Cqrs.Ninject.Azure.ServiceBus.EventBus
Use Ninject as your IoC container of choice when using Microsoft Azure ServiceBus for CQRS.NET as your event bus
Cqrs.Ninject.InProcess.CommandBus
Deprecated. Use the Cqrs.Ninject package instead.
Cqrs.Ninject.Azure.DocumentDb
Use Ninject as your IoC container of choice with Microsoft Azure DocumentDB for CQRS.NET
Cqrs.Ninject.InProcess.EventBus
Deprecated. Use the Cqrs.Ninject package instead.
Cqrs.Ninject.InProcess.EventStore
Deprecated. Use the Cqrs.Ninject package instead.
Cqrs.Sql
The built-in, Sql Store in the CQRS.NET cannot process non-primitive properties on the entity classes in read stores and data stores. If your entity classes require more comp[lexity than just basic, flat primitive property structures, this package will allow you to use Microsoft SqlServer as an read store and data store in CQRS.NET allowing you to build custom converters to provide mappings from your entities to you SQL table schema structures.
cdmdotnet.StateManagement
C# State Management provides a consistent abstraction to accessing data from various collections such as thread bound contexts, HTTP Request and Response collections as well as HTTP Cookies.
Cqrs.Ninject.ServiceHost
Use Ninject as your IoC container of choice to use WCF with CQRS.NET as ServiceHosts
_EnterpriseLibrary.Azure.TransientFaultHandling.ServiceBus.NetCore
A port of EnterpriseLibrary.TransientFaultHandling.ServiceBus for .Net Core The Transient Fault Handling Application Block for Windows Azure ("Topaz") makes your Windows Azure application more resilient to transient failures by providing intelligent retry logic mechanisms.
cdmdotnet.AutoMapper
A lightweight framework for automatically mapping values from one class to another.
Cqrs.Akka
Use Akka.NET actors in CQRS.NET
MYOB.AccountRight.API.SDK.Core
A .NET CORE library SDK wrapper around the MYOB AccountRight API v2. Samples of how to use this API can be found on Github (MYOB-Technology).
Cqrs.Ninject.Azure.Wcf
Use Ninject as your IoC container of choice with Microsoft WCF for CQRS.NET
Cqrs.Ninject.Akka
Use Ninject as your IoC container of choice with Akka.Net for CQRS.NET
42 more packages load after hydration.