Hi, Dave...

Thanks for the links. The code sample helped...I also found a similar one on www.c-sharpcorner.com. So I understand this a little better.

I have two follow-up questions. Probably stupid questions, but I'm still learning...

1) In the code samples that I've seen for remoting, the TCP channel (or HTTP channel) that is used is referenced through 'localhost'. If I want to call a DLL/assembly that's on another machine, how would I reference it? (or...just by virtue of the fact that the server object is loaded and running, would the client 'find' it, or does there need to be another reference?

2) This one is a bit deeper, but is related to #1. We've gone back and forth internally about the use of Web Services vs Remoting in our app [and I believe I received some responses from you about a month ago on remoting].

We have about 150 users across the country who need access to a rich UI. So we use WinForms at the user end, and send data back and forth to the server in DataSets. We have a Web Service, running on a Web Server, that serves as a 'service requestor'...basically, receives the request from the remote client and calls the appropriate function(s) in the middle tier, and then passes result sets back to the end user.

Since the middle tier logic will likely reside on a different computer than the Web Service, that's when we realized that we needed remoting. That's what led to my question about where to 'specify' the location of the middle-tier server.

But it's also led to more general questions, like...

a- Why do we even need the Web Service? Can't we just use HTTP and have the local WinForm use remoting to call the middle-tier? However, is that even a 'web-based' strategy, and is it potentially less secure?

b- Is the approach of
'Client calls Web Service',
'Web Service remotes with Middle-Tier',
'Middle-Tier calls SQL Server',
'Middle Tier returns dataset back to Web Service',
'Web Service sends dataset back to WinForm'...

...an overall sound method, or is there excessive overhead?

While not definite, we've been told to expect that our client may place a firewall in front of the Web Service, and might also place a firewall between the Web Service and the middle-tier for additional security...I mention this in case that factors in to the best overall approach.

Sorry to ask so many questions, but I/we are really in need of advice from those with any experience in this!

Thanks in advance,
Kevin