ASP.NET and Remoting

Question

I have a .net application running on server. Now I want to comunicate between my ASp.NET website and the server application. Currently I use database, server writes info to the db and site uses it etc. However adding new fields to echange and exchanging complex object is a pain. Is remoting the way out? If yes, what are the common things to keep in mind while doing this.

1. both server and asp.net site is on the same server
2. both is under my control
3. is there any other better way than using remoting?
4. It is .NET 2.0

Answer 1

The purists will say that remoting is an old, dead technology, and the way to do it now is to use WCF.

Answer 2

If you're attempting to have some SOA thing, the best thing is to a web service for your server application and access it from your ASP.net website application. It's the best way to do.

However I don't really understand what the purpose of the "server" is? Couldn't your ASP.net website - as you say - be your front-end of the server application?? Your "server" would then simply be the business and data layer and there would be no need to use remoting or WCF.

Answer 3

I would say webservices if want to stay .net 2.0, otherwise it think you should take a look at WCF.

Answer 4

If you need direct interaction between assemblies (ASP.NET and some server application or service) you should use Application Domains and cross-domain calls (some good example here) or using WCF, which is better. Also you can use web services if your server application can be accessed via web without major resulting drawbacks (security issues, server deployment change, etc.).