Merge pull request #27 from Havret/add_ci

NO-JIRA: Configure continuous integration
tree: 86334635b07c0fca7ee3fc365736417431896294
  1. .gitignore
  2. .travis.yml
  3. LICENSE.txt
  4. NOTICE.txt
  6. apache-nms-amqp.sln
  7. appveyor.yml
  8. package.ps1
  9. src/
  10. test/


Build Status


The goal of this project is to combine the .NET Message Service API (NMS) with the Advanced Message Queuing Protocol (AMQP) 1.0 standard wireline protocol. Historically, the Apache community created the NMS API which provided a vendor agnostic .NET interface to a variety of messaging systems. The NMS API gives the flexibility to write .NET applications in C#, VB or any other .NET language, all while using a single API to connect to any number of messaging providers. The Advanced Message Queuing Protocol (AMQP) is an open and standardized internet protocol for reliably passing messages between applications or organizations. Before AMQP became a standard, organizations used proprietary wireline protocols to connect their systems which lead to vendor lock-in and integration problems when integrating with external organizations.

The key to enabling vendor independence and mass adoption of technology is to combine open source APIs and standard wireline protocols which is precisely what this project is all about. Here's how AMQP 1.0 support within NMS helps the .NET community:

  • More Choice: As more message brokers and services implement the AMQP 1.0 standard wireline, .NET developers and architects will have more options for messaging technology.
  • No Migration Risk: Since AMQP 1.0 is a wireline standard, you won't run into the problems that used to happen when switching between implementations.
  • Innovation: Competition is a key component of technology innovation. Directly competitive messaging implementations, with seamless pluggability, forces vendors to innovate and differentiate.

If you are a .NET developer that doesn't want to be locked into a messaging implementation then get engaged with this project. Here you will find the open source code base and please provide comments and make your own enhancements. The project will be folded into the Apache community once fully mature.

AMQP1.0 Protocol Engine AmqpNetLite

Apache-NMS-AMQP uses AmqpNetLite as the underlying AMQP 1.0 transport Protocol engine.

Overall Architecture

Apache-NMS-AMQP should bridge the familiar NMS concepts to AMQP protocol concepts as described in the document amqp-bindmap-jms-v1.0-wd09.pdf. So in general most of the top level classes that implement the Apache.NMS interface Connection, Session, MessageProducer, etc create, manage, and destroy the amqpnetlite equivalent object Connection, Session, Link, etc.

Building With Visual Studio 2019

There are multiple projects: Apache-NMS-AMQP, Apache-NMS-AMQP.Test, and HelloWorld. All projects use the new csproj format available in Visual Studio 2019. Apache-NMS-AMQP is the library which implements The Apache.NMS Interface using AmqpNetLite. Apache-NMS-AMQP.Test produces an NUnit dll for unit testing. HelloWorld is a sample application using the NMS library which can send messages to an AMQP Message Broker.

To build, launch Visual Studio 2019 with the nms-amqp.sln file and build the solution. Build artifacts will be under <root_folder>\<project_folder>\bin\$(Configuration)\$(TargetFramework).

Building With DotNet SDK

Alternatively, to build without Visual Studio 2019 the project can be built using .NET Core sdk tool, version 2.2.+. Execute the dotnet sdk command to build all projects:

<root_folder>>dotnet build nms-amqp.sln 


Tests use the NUnit Framework. The tests include both unit and system tests (require a broker).

Apache-NMS-AMQP-Test contains only unit tests and doesn't require any configuration and dependencies.

Apache-NMS-AMQP-Interop-Test contains system tests and require broker to be up and running. Broker can be configured either directly from the code (to do so you have to edit AmqpTestSupport base class), or using environment variables:

NUNIT3-CONSOLE Apache-NMS-AMQP-Interop-Test.dll -p:uri=brokerUri -p:cu=userName -p:cpwd=password

VS2019 Test Explorer

Visual Studio 2019 will also run NUnit tests with the built-in TestExplorer tool.

dotnet test

If building with the dotnet sdk, From the top level directory simply enter dotnet test to build and run all the tests. Individual tests can be run with:

dotnet test filter=<Test Name>

Amqp Provider NMS Feature Support

TLS/SSLYConfiguration is supported using transport properties.
Client Certificate AuthenticationYConfiguration is supported using transport properties.
Transactions (AcknowledgementMode.Transactional)Y
Distributed Transactions (INetTxConnectionFactory, INetTxConnection, INetTxSession)N
IObjectMessageY *Amqp value object bodies and dotnet serializable object bodies are supported.
IConnectionYThe ConnectionInterruptedListener event and the ConnectionResumedListener are not supported.
ProducerTransformerDelegateNAny member access should throw a NotSupportedException.
ConsumerTransformerDelegateNAny member access should throw a NotSupportedException.
IMessageProducerY *Anonymous producers are only supported on connections with the ANONYMOUS-RELAY capability.
MsgDeliveryMode.PersistentYProducers will block on send until an outcome is received or will timeout after waiting the RequestTimeout timespan amount. Exceptions may be throw depending on the outcome or if the producer times out.
MsgDeliveryMode.NonPersistentYProducers will not block on send nor expect to receive an outcome. Should an exception be raised from the outcome the exception will be delivered using the the connection ExceptionListener.
IMessageConsumerY *Message Selectors and noLocal filter are not supported.
Durable ConsumersY
IQueueBrowserNThe provider will throw NotImplementedException for the ISession create methods.
Configurable NMSMessageID and amqp serializtionNFor future consideration. The prodiver will generate a MessageID from a sequence and serialize it as a string.
Flow control configurationNFor future consideration. The provider will use amqpnetlite defaults except for initial link credits which is 200.
Object Deserialization PolicyNFor future consideration. The provider considers all Dotnet serialized objects in Object Message bodies are safe to deserialize.


This software is licensed under the terms you may find in the file named “LICENSE” in this directory.