Database Reference
In-Depth Information
Even if we know that MSMQ is set up correctly (because we have tested it), we may need
to know which queues it is currently using.
Using the PowerShell
PM> Get-NServiceBusLocalMachineSettings
com-
mand, we can see which queues it currently wishes to reference. Also, by viewing Visual
Studio Server Explorer, we can verify that they are present.
One of the many features I really like about NServiceBus is its ability to create message
queues, services, and DTC pieces. This is less work than what the server staff does to
maintain and install an application.
Here is a look at the queues now in Visual Studio Server Explorer:
We can see the RavenDB service is running without even leaving Visual Studio by look-
ing into the services section of the same Visual Studio Server Explorer in which it was in-
stalled.
RavenDB is a document-oriented database that can operate completely independent of
NServiceBus. This means that you are now working on NoSQL development, and it has
an interface to save the collections of objects.
RavenDB must be running as NServiceBus uses it to store internal information such as
subscription endpoint information and message types. The following screenshot is of
Server Explorer in Visual Studio and shows that RavenDB is running:
