I am having some difficulty in deciphering the different approaches to
remoting. We need to call methods on remote objects hosted in IIS on a
different app server from the code behinds of our ASP.Net pages.

Basically, all the objects are built and functioning without remoting
currently (i.e. the objects we want to remote are currently local to the
client web application).

We also want to make this change with as little disruption to the source
code as possible. And we want to use Binary over HTTPS. So, how do we do
this?

Ny initial feeling is that we would:

- Add Remoting to references & imports statement to remoteable classes
- Inherit from MarshalByRefObject
- Recompile each remoteable class
- Create a proxy for each of these objects (using SoapSuds.exe or ???)
- Remove the original versions of the now remoteable dlls from the client app
- Remove the references to the original non-remoteavble objects from each
client page
- Add the proxies to the client application
- Add the new references to the new proxies to each page (as necessary)
- Rebuild the client ASP.Net application
- Deploy the client application
- Deploy the new proxies on the client web server in the appropriate folders

How close is this? Do I need to add further configuration information to
the web.config files on either the client or server, or both?

Thank you in advance.