Made sure we setup the HubContext properly.
- Set the Groups property in the HubContext.
- Added tests to verify sending messages outside of the hub works.
Ignore xml doc comment warnings
Prevent sending ClientHubInvocation to clients.
Trigger stateChanged after the connection state has actually changed.

Fixes Issue #598
Changed the order in which the iframe for foreverFrame gets added to the body

#718
Trigger stateChanged after the connection state has actually changed.

Fixes Issue #598 for the .NET client.
Fixed previous fixes to Issue #598

Fixed bug in JS and .NET clients where StateChanged events would be passed a
copy of the new state in lieu of the old state.
Removed the id and deferral objects on connection stop.

#727
After testing the last commit changes I had to revert a few things.

Also added the unbinding of the UpdateKeepAlive on the stop monitoring
of keep alive.  Lastly added comments and cleaned up functions within
the common transports file.

#795
Changed all uses of $.trigger to $.triggerHandler
Removed AjaxMin from hubify.exe in preparation for merge into signalr.exe
 - Users can minify the output of hubify.exe with whatever minifier they like
Remove automatic MapHubs call from ASP.NET host

Fixes Issue #790
Updated .nuspecs so manually included framework specific dlls get packaged.

This was broken after the output path was changed to the artifacts directory.
Fixes Issue #804.
Import the common target before the Silverlight and WP7 targets.

This ensures that changing the OutputPath to the artifacts directory works.
Placed a _ on the deferral object off connection.

The deferral object is not supposed to be used by consumers, hence the
prefixing it with _

#727
Renamed createProxy to createHubProxy in the JS client and .NET client.
Fixed api change in stress.
Updated the scripts.
Fixed issue causing clients in the drawingpad sample to rebroadcast draws
Added logic in reconnect to detect if the connection has been forcibly disconnected.

The reason why this logic is necessary is that the onclose for websocket
is what triggers a reconnect.  However if we forcibly stop a connection
via $.connection.hub.stop() the websockets reconnect gets triggered.
This is expected because we close the socket.  This is also what helps
websockets reconnect on network loss which is why we can't just add the
logic in the onclose handler.

#823