Mitch posed a question to me about the future of .Net Remoting.  First off .Net Remoting is fully supported in version 2 of the .Net Framework.  However, the long term direction of Microsoft is WCF aka Indigo.  WCF is the merging of several different technologies which includes ASMX, Remoting, MSMQ, Com+ Enterprice Services.

Which brings up a interesting question, should you consider migrating when WCF released late next year?

In my HMO it comes down to how your application is architected and how your application is being used.

First, if you implemented your Remoting calls using interfaces, porting your code from Remoting to WCF shouldn't be  to hard.  Especially if your followed a layered design.  Futhermore, I little known feature that was added in Beta 2 of .Net 2 allows you to use interfaces to declare your operations (Web Methods) in ASMX 2.0!

Second, what features do you gain by migrating?  Here's a great break down of the features in WCF as well as ASMX and WSE.

Third does your application require inter-op for other platforms (Java)? If the answer is no, it might make sense to postpone your migration until the cost can be justified.

Finally I'd like to make a distinction between port and migration.  Porting to me means making the smallest possible changes in order to run an application under a new technology.   Migration on the another hand typlically involve some level of refactoring.