Hi Dwight,

If your service code is written in SQLCLR, the way I debug is through Visual
Studio using "Attach to process". You must attach to the SQL Server process
itself (SQLSERVER.EXE) and if the SQL Server service isn't running as you
(it shouldn't be), you need to check "show processes from all users" to be
able to select it. You should only do this type of debugging on your own
test instance because, as the message box says "using attach to process
could be harmful to SQL Server" (I've had it bring down the SQL Server
process on occasion, due to "pilot error"). You must be running VS as a SQL
Server sysadmin for debugging to work.

Ensure you have the .pdb file for your assembly cataloged (using ALTER
ASSEMBLY ADD FILE ...). Start the debugger, set breakpoints, hit the queue
with a message and the service program should spin up and hit your
breakpoint.

If you're using T-SQL activation proc you can directly debug service
programs, but you can insert PRINT statements into the T-SQL code. The PRINT
statement output will appear in the SQL Server log file. Use SSMS to read
the log.

I haven't got ShoppingCart in front of me, but if there is no BrokerMethod
for the Invoice message type, it's likely being sent by the application not
processed from a BrokerService activator. Search the source for BEGIN DIALOG
CONVERSION (DIALOG keyword is optional) followed by a separate SEND of the
message type.

Hope this helps,
Bob Beauchemin
SQLskills