Hi all,
I have a small windows app I making that is supposed to use a couple of
remote objects on a different server other than my own. To start with, I
had it all setup locally and was working fine, the objects would get
instantiated and I could use them no problem. The original setup consisted
of a windows console application used to serve up the calls to the remote
objects, a client app and the remotes themselves in a class library. I then
wanted to have these remotable objects (dll) & web.config file hosted under
IIS on the new server and test by connect using my client. So I adjusted my
client app's config file to use this new server's IP address except I didn't
add in the IP address in the wellknown config setting to see what kind of
error it would throw like the following:
<wellknown url="http:// IPADRESSOFSERVE R/PlaylistRemote/PlaylistRemote. soap"
type="Remotable s.PlaylistRemot e, plrem" />
So it would seem it is not using my config file, but it seems the objects
are getting created anyways, even with removing & re-adding the reference to
the remotable project in my client app, rebuilding & re-deploying the
objects are still getting created.
I have made a virtual directory (used this name in my url above), placed my
remote class library in a new bin folder, and placed my web.config file in
the virtual directory. How can the remote objects get instantiated without
the url being correct in the config file? Is it still using the old set up
somehow? Any help would greatly be appreciated.
Cheers, Joe :)
I have a small windows app I making that is supposed to use a couple of
remote objects on a different server other than my own. To start with, I
had it all setup locally and was working fine, the objects would get
instantiated and I could use them no problem. The original setup consisted
of a windows console application used to serve up the calls to the remote
objects, a client app and the remotes themselves in a class library. I then
wanted to have these remotable objects (dll) & web.config file hosted under
IIS on the new server and test by connect using my client. So I adjusted my
client app's config file to use this new server's IP address except I didn't
add in the IP address in the wellknown config setting to see what kind of
error it would throw like the following:
<wellknown url="http:// IPADRESSOFSERVE R/PlaylistRemote/PlaylistRemote. soap"
type="Remotable s.PlaylistRemot e, plrem" />
So it would seem it is not using my config file, but it seems the objects
are getting created anyways, even with removing & re-adding the reference to
the remotable project in my client app, rebuilding & re-deploying the
objects are still getting created.
I have made a virtual directory (used this name in my url above), placed my
remote class library in a new bin folder, and placed my web.config file in
the virtual directory. How can the remote objects get instantiated without
the url being correct in the config file? Is it still using the old set up
somehow? Any help would greatly be appreciated.
Cheers, Joe :)