.NET-wise, you have a few options:
You will always need a Java NIOServer in your setup but you don't need
to write any Java code, just start it and treat it as a standalone
process.
To start the server from the command-line, you'll need java installed,
and the JARs from the StreamHubSDK in the same directory, then try:
java -cp .;streamhub-2.0.11.jar;log4j-1.2.14.jar;json-20080701.jar
com.streamhub.nio.NIOServer 8888 8889
This will start the server on port 8888 and open a streaming adapter
port on 8889.
The Streaming Adapter port is where you connect the .NET Streaming
Adapter SDK to. This is where you write your .NET code to push data
out to clients. Download the latest version of the .NET Streaming SDK
from: http://www.stream-hub.com/downloads/StreamHubStreamingAdapterSDK-1.0.1.12.zip.
Client-wise is where the options come in, if you are developing a .NET
web project using ASP.NET, then you'll probably be best of using the
Ajax SDK - its essentially just a JavaScript file you'll need to
include in any pages which connect to StreamHub. The Ajax SDK is
included with the server in the main download available here:
http://www.stream-hub.com/download.html.
If you're developing a .NET Desktop client, you'll need to use the
the .NET Client SDK available here: http://www.stream-hub.com/downloads/StreamHubClientSDK-1.0.1.22.zip
In summary there's two .NET SDKs, one server-side (StreamingAdapter)
and one client-side (ClientSDK), but you'll always need the Java
server in the middle. And you'll only need the client-side SDK if
you're writing a Desktop client otherwise use the Ajax SDK.
Hope this helps clear things up a bit for .NET people.