.Net Remoting, is it still relevant?
-
Probably not so much. Basically it was a way to implement Remote Procedure Calls (RPC) - expose functionality to other apps. Now there are other (better and simpler) ways to implement that functionality. WCF (though it was complicated at one point in history) is far more prevalent now (maybe the default for C#?) Now you can quite easily create a self-hosted app and expose functionality. (of course, security is always a challenge and a necessity). Check this out and you can get an overview of how much simpler it can be than the old days of .NET Remoting. How to: Host a WCF Service in a Managed Application | Microsoft Docs[^] Update Here are a couple of SO entries that were basically asking same question that I just found. Custom RPC vs WCF vs .NET Remoting - Stack Overflow[^] c# - Does WCF really replace .NET Remoting? - Stack Overflow[^] That last one was posted 9 years ago and even then the reply was, "remoting is old". :)
-
That's a name I haven't heard in a long time. A long time.
May the fourth be with you.
Sent from my Amstrad PC 1640 Never throw anything away, Griff Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
-
When is the last time you worked on .Net Remoting? Potential opportunity but I don't think I'd like the work.
.NET Remoting .. if it pays for the insanity afterward..maybe.....
Caveat Emptor. "Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
-
When is the last time you worked on .Net Remoting? Potential opportunity but I don't think I'd like the work.
The first book I got on .Net was Petzolds book on remoting, never used it and went on to simpler things.
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP
-
When is the last time you worked on .Net Remoting? Potential opportunity but I don't think I'd like the work.
-
When is the last time you worked on .Net Remoting? Potential opportunity but I don't think I'd like the work.
used it for 7ish years back in the day for last company's flag ship product for communication between computers, it worked well, then WCF came out; and I believed the hype that it was so much better, and restructured the system for a big new release around WCF. In the long run it wasn't anything spectacular and I don't think it improved anything, now according to the latest news WCF will not be carried forward into Dotnet 5. before that news came out though we had already made the commitment to leave WCF and start using REST services, it was more flexible and I could tie our java products into the same calls as the .net projects with no extra work.
-
(If I'm right) As part of API/Framework standardization, Soon this would be marked Obsolete & ultimately removed from the framework. Migrate or die type. :)
MS already said the same thing about WCF not too long ago about future versions of dotnet[^]
-
When is the last time you worked on .Net Remoting? Potential opportunity but I don't think I'd like the work.
I just recently left my last job, and they supported it quite heavily. The applications were extremely old. I avoided it as much as possible, but the little I did learn came down to you could replace the entire system with web services, of one flavor or another, and make life very easy. If I had to explain it to somebody who had never seen it, I would say .Net Remoting was the grandfather of web services, before anybody know what web services were. One of the many problems that we faced, in working with Remoting, was the code had been built in Visual Studio prior to 2005. That was our guess anyway. We didn't have any licenses for an IDE that would work on it, and it was next to impossible to make changes. The programs that used it were on a 6 months cycle that lasted 3 months. They ran data in March through June and then again in September through November. That left us only 3 months to rewrite everything before the software had to be ran again and it was a fairly large and complex system. In general, dealing with it sucked. I don't know the final outcome but the program was on the board for a modernization to using web services.
-
When is the last time you worked on .Net Remoting? Potential opportunity but I don't think I'd like the work.
-
Probably not so much. Basically it was a way to implement Remote Procedure Calls (RPC) - expose functionality to other apps. Now there are other (better and simpler) ways to implement that functionality. WCF (though it was complicated at one point in history) is far more prevalent now (maybe the default for C#?) Now you can quite easily create a self-hosted app and expose functionality. (of course, security is always a challenge and a necessity). Check this out and you can get an overview of how much simpler it can be than the old days of .NET Remoting. How to: Host a WCF Service in a Managed Application | Microsoft Docs[^] Update Here are a couple of SO entries that were basically asking same question that I just found. Custom RPC vs WCF vs .NET Remoting - Stack Overflow[^] c# - Does WCF really replace .NET Remoting? - Stack Overflow[^] That last one was posted 9 years ago and even then the reply was, "remoting is old". :)
-
.NET remoting is the same dead-born technology as WCF, EF, WF, you name it. Simply because MS don't have even 5 smart guys to make good, perspective product.
Yes, these frameworks required architecting, and all the cool boys just wanted to sit down with something shiny new and code, so no buzz.
-
used it for 7ish years back in the day for last company's flag ship product for communication between computers, it worked well, then WCF came out; and I believed the hype that it was so much better, and restructured the system for a big new release around WCF. In the long run it wasn't anything spectacular and I don't think it improved anything, now according to the latest news WCF will not be carried forward into Dotnet 5. before that news came out though we had already made the commitment to leave WCF and start using REST services, it was more flexible and I could tie our java products into the same calls as the .net projects with no extra work.
Matt McGuire wrote:
we had already made the commitment to leave WCF and start using REST services, it was more flexible and I could tie our java products into the same calls as the .net projects with no extra work.
Yep, that's the way to go!! :thumbsup::thumbsup::thumbsup:
-
MS already said the same thing about WCF not too long ago about future versions of dotnet[^]
