Remote Device Link

No client connected!

Local Developer Mode

Connect a client with: 

c:\inetpub\RemoteDeviceAdmin.Client.Console\bin\Debug\RemoteDeviceAdmin.Client.Console.exe -s http://www.remotedevice.link 10.0.0.123

Be sure to substitute the 10.0.0.123 IP with a local IP you wish to connect to. The client will display the URL to use for access.

Note that when running with localhost, this special "developer" mode is activated, which removes the security checks and proxies requests to all (typically: one) clients.

Realistic Setup

For a more realistic setup, you can host in IIS and use a wildcard DNS that maps to 127.0.0.1, such as http://localhost.me.

Since this runs in IIS instead of VisualStudio, if you want to debug this you'd have to explicitly attach a debugger to the IIS process.

  1. In your local IIS, set up a new site with:
    • Physical path: c:\inetpub\rdl-legacy-2.0.468\
    • Hostname: *.localhost.me
  2. Edit the site's Bindings and add the hostname localhost.me
  3. Connect a client using: 
    c:\inetpub\RemoteDeviceAdmin.Client.Console\bin\Debug\RemoteDeviceAdmin.Client.Console.exe -s http://localhost.me 10.0.0.123
  4. You should now be able to visit the URL displayed by the client (such as http://abcde123456789.localhost.me) in your browser to use the proxy.