Hector,

I've not used Remoting either ... we use WebServices exclusively ... that's the only reason I mentioned it as a possible alternative (notice that I said "possible" <g>).

~~Bonnie


>Bonnie/Rodney,
>
>I have not personally used Remoting, not to mention done a seed comparison between WS and Remoting. However, early this year, at VS Live conference, I heard several of the speakers encouraging developers to look closely at Remoting since it provides better performance and richer programming model than WS.
>
>Keep in mind however, that I have not played with this. I am just letting you know what I've heard. I feel like a "real" consultant today :)
>
>>
>>Another option might be to avoid remoting altogether and access your server-side components via WebServices.
>>
>>~~Bonnie
>>
>>>Hi,
>>>
>>>I am working on a three tier web app, with a C# business tier that is accessed using remoting, and a SQL server database. I am preparing for implementation, and I am confused as to what type of remoting configuration to use. Currently, I have the middle tier running as a windows service on the development server. However, after reading Advanced .NET remoting from Ingo Rammer, I'm not sure that the architecture I have will work. The remoting objects are accessed using a TCP connection and an open port number. After reading the Configuration and Deployment section of the aforementioned book, I am not sure if people coming from the Internet will be able to use the TCP method of connecting through the firewall.
>>>
>>>Hosting the remoting objects in IIS would solve my problem, but incur a performance penalty. If anyone has attempted anything like this, could you let me know what you did, and why? Any information would be appreciated. I would like to get an idea what would work best, before I start to rework the code.
>>>
>>>
>>>Thanks,
>>>
>>>Rodney