Is this working? I added it to a test and it triggers an exception when started

[SolidSoftwareServices]

No description provided.

[CyAScott]

Just to make sure, I reran the unit tests and it all passed. I have a few questions about the machine and environment you are using to run these tests.

• Is it a 64 bit Windows machine?
• Is Visual Studio 2013 or Redistributable Packages for Visual Studio 2013 installed on your machine?
• In your Visual Studio solution folder there should a packages folder where your nuget packages are stored. In that folder is there both an Erlang.OTP.64bit.18.3.0 and RabbitMQ.3.6.2 folder?
• In the nuget packages folder: packages\Erlang.OTP.64bit.18.3.0\tools\binary\bin. Run the erl.exe file. Does the console output look like the text below:

Eshell V7.3  (abort with ^G)`
1>

Assuming yes for all the above questions. Try running the batch script below:

SET RABBITMQ_BASE=C:\\SomePathForRbbit2GoToUse\\
SET RABBITMQ_PLUGINS_DIR=<path to the nuget packages folder>\\RabbitMQ.3.6.2\\tools\\binary\\plugins\\
SET ERLANG_HOME=<path to the nuget packages folder>\\Erlang.OTP.64bit.18.3.0\\tools\\binary\\

"<path to the nuget packages folder>\RabbitMQ.3.6.2\tools\binary\sbin\rabbitmq-server.bat"

The RABBITMQ_BASE variable can be any folder that exists. You will need to replace the<path to the nuget packages folder> parts with where the nuget package folder is. Keep in mind that the paths for the RABBITMQ_BASE, RABBITMQ_PLUGINS_DIR, and ERLANG_HOME variables use \\ instead of \ to separate the directory names and that every folder path ends with \\.

When you run the script, you should see the something similar to this:

              RabbitMQ 3.6.1. Copyright (C) 2007-2016 Pivotal Software, Inc.
  ##  ##      Licensed under the MPL.  See http://www.rabbitmq.com/
  ##  ##
  ##########  Logs: Some Log File Path
  ######  ##        Some Log File Path
  ##########
              Starting broker... completed with 0 plugins.

When you get this output then that means you are running RabbitMq. This nuget package follows the same process shown above. Something to be aware of is that RabbitMq may need an exception added to your firewall settings. Usually windows will prompt you add the exception when RabbitMq first starts. If you were able to get RabbitMq started manually and are still have problems let me know.