193 packages tagged with “publish”
**NOTE** For .NET 6 upwards we recommend NATS.Net package - NATS acts as a central nervous system for distributed systems at scale for IoT, edge computing, and cloud native and on-premise applications. This is the .NET client API.
This package has been deprecated. An update will remove the current use of this package from the project and replace it with a reference to the 'NServiceBus' nuget.
Use this for EventHub distributed partition processing. For more information please visit http://go.microsoft.com/fwlink/?LinkID=403957 Please note that a newer package Azure.Messaging.EventHubs.Processor is available as of February 2020. While this package will continue to receive critical bug fixes, we strongly encourage you to upgrade. Read the migration guide at https://aka.ms/azsdk/net/migrate/eh for more details. This package requires at least .Net Framework 4.6.2.
NATS acts as a central nervous system for distributed systems at scale for IoT, edge computing, and cloud native and on-premise applications. This is the .NET Streaming client API.
This packages has been deprecated. An update will remove the current use of this package from the project.
This gives your non web projects the ability to be put into a published folder, just like your web project does when being built outside of visual studio. Not entirely sure what this means? Check out the project url (on the left) and/or watch the video: http://www.youtube.com/watch?v=-oPtsb11vBU
Pub/Sub in-memory with all parts configurable
An implementation of the EventAggregator pattern.
Framework for enabling time-series data processing services including hosted input, action and output adapter implementations.
ActiveMQ support for NServicebus
The endpoint plugin to connect an endpoint to Service Control
These packages include the resources needed to write Remote Data Adapters and Remote Metadata Adapters for Lightstreamer Server with .NET. Each Lightstreamer session requires the presence of an Adapter Set, which is made up of one Metadata Adapter and one or multiple Data Adapters. Multiple Adapter Sets can be plugged onto Lightstreamer Server. Please refer to the provided "General Concepts.pdf" document for further details about the role of the Adapters in Lightstreamer, and in particular to this documentation https://lightstreamer.com/docs/ls-server/latest/Adapter%20Remoting%20Infrastructure.pdf for Remote Adapters deploying. The full API references are available from https://lightstreamer.com/sdks/ls-dotnetstandard-adapter/1.15.2/api/index.html
The WebServices Integration for the nservicebus, The most popular open-source service bus for .net
An easy wrapper for the RabbitMQ client that allows inclusion in DotNetCore projects. Can be used with the standard dependency injection provided in DotNetCore.
Enables audit of Saga state changes
Please note, for Azure Service Bus, Azure Event Hubs and Azure Relay, newer packages Azure.Messaging.ServiceBus, Azure.Messaging.EventHubs and Microsoft.Azure.Relay are available as of November 2020, February 2020 and March 2017 respectively. While WindowsAzure.ServiceBus will continue to receive critical bug fixes, we strongly encourage you to upgrade. Read https://aka.ms/azsdk/blog/msging/intro for more details. It adds Microsoft.ServiceBus.dll along with related configuration files to your project. This library allows AMQP 1.0 to be used as one of the protocols for communication with Microsoft Azure Service Bus. For more information on Messaging features, please visit: http://azure.microsoft.com/en-us/documentation/services/service-bus/ For more information on Event Hub features, please visit: http://go.microsoft.com/fwlink/?LinkID=403957 Please note that this package requires at least .Net Framework 4.6.2.
The Notifications component for the NServicebus
Use this with Windows Azure Service Bus and Notification Hubs client registration (for Windows Store and Windows Phone 8 apps). It adds Microsoft.WindowsAzure.Messaging.Managed.dll to your project. This package is for developing Windows Store and Windows Phone 8 applications with C# (managed)
Distributor for MSMQ for the nservicebus
PowerShell Cmdlets for NServiceBus
Emitter is an MQTT client tailored for emitter.io service, allowing real-time publish subscribe. It supports full .Net Framework, .Net Micro Framework and WinRT platform (Windows 8+ and Windows Phone 8+).
A simple publish/subscribe service bus contract
Class library adding support for the Publish/Subscribe extension (XEP-0060) to the XMPP Client library defined in Waher.Networking.XMPP.
Example of SignalR with F-Sharp (and Silverlight 5 or Javascript): - SignalR is a library (for web-based Publish/Subscribe -pattern) on top of WebSockets, which is HTML5 API that enables bi-directional communication between the browser and server. SignalR will fallback to other techniques and technologies when WebSockets are not available. http://signalr.net/ - F-Sharp (F#) is multiparadigm (functional-first) programming language mainly for .NET environment. http://fsharp.org/ - This sample uses Reactive Extensions 2.1 to communicate with SignalR, on both client and server side. Reactive Extensions is a library to compose asynchronous and event-based programs using observable collections and LINQ-style query operators. http://msdn.microsoft.com/en-us/data/gg577609.aspx - For server side: This could work purely from F# as Owin (http://owin.org/) console application but now F#-server-side is called from an empty ASP.NET C# Web Application. (Still you can start OWin from F# Interactive...) - For client side: Silverlight 5.0 application using F#-library and Silverlight 5.0 XAML/C# application to show the user interface. http://www.silverlight.net There is also jQuery/JavaScript test page, if you don't want to use Silverlight. - This proof of concept/sample/tutorial/demo is developed with Visual Studio 2012. References are resolved via NuGet. F# compiler won't auto-restore packages on compile. So go first to Tools -> Library Package Manager -> NuGet and press "Restore" to restore all the references, and then rebuild. - SignalR supports two kinds of connections: Hub and PersistentConnection Both are working with Silverlight and JavaScript.
The Lightstreamer .Net Standard Client SDK allows to subscribe to real-time data pushed by a Lightstreamer server and to send any message to the server. The library offers automatic recovery from connection failures, automatic selection of the best available transport, and full decoupling of subscription and connection operations.
Return to source queue and licensing tools for uses with NServiceBus
A RabbitMQ implementation of a simple publish/subscribe service bus