I'm trying to run this up locally to connect to an existing session using a code.

I've been able to use the ClientLaunchParameters class as described elsewhere in the forum and lifted the various parameters by looking at the click once download URL in firebug. I can get my test app to fire up the exe with the params and connect successfully.

I'm now trying to integrate the session manager/create session stuff which think allows me to pass up the simple key and get back the encryption key/session etc.

My app references the following DLL files:
Elsinore.ScreenConnect.Core.DLL
Elsinore.ScreenConnect.Server.DLL

However, when I pull both these into my vs2010 (console) test app, they seem to be in confict with each other and I lose sight of what's in the server DLL file. I tried aliasing one, but VS2010 seems to have a bug with this stuff.

I'm wondering if I'm doing something wrong (given I can't find any references to this sort of issue elsewhere in the forum).

Gordon

Yep, 4.0 assemblies are not binary compatible with ours which are 2.0/3.0/3.5 compatible. Let us know if you need anything else.