Would you consider adding some or all of this change?

Hi,

Very nice project.  It makes looking through NSB queues so much easier than using 'Computer Management'.

One small problem though.. I had an issue in my environment where Profiler wouldn't connect to remote machines.  After a lot of head scratching, it turns out calling MessageQueue.GetPrivateQueuesByMachine() would return unusable queues in my environment.  I was tinkering around in the debugger and came to the conclusion that simply assigning the queue.Path property (to an identical value) resolved the issue for reasons unknown so I submit the attached change.

Thanks,
-Bill

Environment ( It's not by choice  ;-]   )
Local - Windows 7 64 bit, no domain
Remote - Windows 2003 Server, no domain
Accounts = same name
Passwords = same

Patch Notes:

-Fixed issue connecting to remote queues that may be specific to Windows
2003 Server and/or MSMQ Workgroup (authentication) mode.  In my environment, calling
MessageQueue.GetPrivateQueuesByMachine() on a remote machine would return
queues who's properties couldn't be read and who's messages couldn't be peeked.
-Now only use MSMQ Direct=TCP when connecting via an IP address.
-When you connect to a machine, you get a new root node in the Explorer. Previously the root node would always be the local machine.