C# WCF Dead or alive?
-
i see a lot of blog posts around the internet that says WCF is Dead, any other thoughts?
What would the replacement be? Web API, maybe? WCF works extremely well for exposing remote methods in your services. Yes, it was previously clogged up with config information but now it's a lot better. It works well and is extremely easy to implement. Why would it be dead, unless there is some simpler replacement?
My book, Launch Your Android App, is available at Amazon.com.
-
i see a lot of blog posts around the internet that says WCF is Dead, any other thoughts?
-
i see a lot of blog posts around the internet that says WCF is Dead, any other thoughts?
It is my "opinion" that these people don't know how to use WCF (or other technology) and don't wish to learn, therefore the technology is now dead. Like a miracle the technology is now dead. It was there a minute ago, but now it is gone. Whatever, WCF is great when used correctly and like others have said, it has gotten better.
-
What would the replacement be? Web API, maybe? WCF works extremely well for exposing remote methods in your services. Yes, it was previously clogged up with config information but now it's a lot better. It works well and is extremely easy to implement. Why would it be dead, unless there is some simpler replacement?
My book, Launch Your Android App, is available at Amazon.com.
I've been looking into SignalR. Very simple and it could be a WCF replacement.
If it's not broken, fix it until it is
-
i see a lot of blog posts around the internet that says WCF is Dead, any other thoughts?
-
Nagy Vilmos wrote:
any other thoughts?
Why do hot dogs come in packs of 10, but hot dog buns come in packs of 8??
If it's not broken, fix it until it is
The chosen one!
This space for rent
-
Nagy Vilmos wrote:
any other thoughts?
Why do hot dogs come in packs of 10, but hot dog buns come in packs of 8??
If it's not broken, fix it until it is
-
The chosen one!
This space for rent
I'm working on an app that will have a component like DropBox. Since SignalR can maintain connections between clients and server, I'm using it to signal the server when a file is uploaded, then the server in turn notifies all clients. Very simple to set up and use. Question: Would you use this to send/receive query results as data sets?
If it's not broken, fix it until it is
-
I've been looking into SignalR. Very simple and it could be a WCF replacement.
If it's not broken, fix it until it is
Kevin Marois wrote:
I've been looking into SignalR
:thumbsup: SignalR is very interesting.
My book, Launch Your Android App, is available at Amazon.com.
-
Kevin Marois wrote:
Why do hot dogs come in packs of 10, but hot dog buns come in packs of 8??
Buy 8 packs of hot dogs, 10 packs of buns, and invite 80 79 friends for a BBQ. No leftovers.
Now why didn't I think I that? oh ya, I don't have 79 friends.
If it's not broken, fix it until it is
-
What would the replacement be? Web API, maybe? WCF works extremely well for exposing remote methods in your services. Yes, it was previously clogged up with config information but now it's a lot better. It works well and is extremely easy to implement. Why would it be dead, unless there is some simpler replacement?
My book, Launch Your Android App, is available at Amazon.com.
raddevus wrote:
It works well and is extremely easy to implement.
Easy you say. I recently picked up a copy of Programming WCF Services and I was suffering from information overload by the end of the first chapter. The shear volume of what can be done in WCF and granularity of the configuration settings can be a little overwhelming when looking at it for the first time. I myself thought that building a service application would be relatively easy until I started reading this book. Now I am a little apprehensive about taking the plunge without further study.
if (Object.DividedByZero == true) { Universe.Implode(); } Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
-
raddevus wrote:
It works well and is extremely easy to implement.
Easy you say. I recently picked up a copy of Programming WCF Services and I was suffering from information overload by the end of the first chapter. The shear volume of what can be done in WCF and granularity of the configuration settings can be a little overwhelming when looking at it for the first time. I myself thought that building a service application would be relatively easy until I started reading this book. Now I am a little apprehensive about taking the plunge without further study.
if (Object.DividedByZero == true) { Universe.Implode(); } Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
I was thinking along the lines of this simple example: Walkthrough: Creating a simple WCF Service in Windows Forms[^] Yes, the technology is huge. It's quite amazing what it does to solve one of the most long-living architectural problems throughout computing history (IPC, RPC, RMI, Remoting, CORBA, DCOM, Web Services, Web API, REST).
My book, Launch Your Android App, is available at Amazon.com.
-
Kevin Marois wrote:
Why do hot dogs come in packs of 10, but hot dog buns come in packs of 8??
Buy 8 packs of hot dogs, 10 packs of buns, and invite 80 79 friends for a BBQ. No leftovers.
dandy72 wrote:
Buy 8 packs of hot dogs, 10 packs of buns, and invite 80 79 friends for a BBQ. No leftovers.
:thumbsup: Ingenius!! Everytime I eat hotdogs from now on I will implement this waste-saving algorithm. :laugh:
My book, Launch Your Android App, is available at Amazon.com.
-
I was thinking along the lines of this simple example: Walkthrough: Creating a simple WCF Service in Windows Forms[^] Yes, the technology is huge. It's quite amazing what it does to solve one of the most long-living architectural problems throughout computing history (IPC, RPC, RMI, Remoting, CORBA, DCOM, Web Services, Web API, REST).
My book, Launch Your Android App, is available at Amazon.com.
I've been through that tutorial before and that's what made me think it would simple. I also wanted to read professional level material so I could build WCF services that would thrive in an Enterprise environment where reliability, security, and the ability to scale must all be addressed. I am picturing my brain as a smoldering pile of ash once I get done learning all of this :laugh:
if (Object.DividedByZero == true) { Universe.Implode(); } Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
-
I've been through that tutorial before and that's what made me think it would simple. I also wanted to read professional level material so I could build WCF services that would thrive in an Enterprise environment where reliability, security, and the ability to scale must all be addressed. I am picturing my brain as a smoldering pile of ash once I get done learning all of this :laugh:
if (Object.DividedByZero == true) { Universe.Implode(); } Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
Foothill wrote:
I am picturing my brain as a smoldering pile of ash once I get done learning all of this
You are a lucky one then. The rest of us had our brains melt and run out our ears. :laugh:
My book, Launch Your Android App, is available at Amazon.com.
-
I've been looking into SignalR. Very simple and it could be a WCF replacement.
If it's not broken, fix it until it is
As far as I know SignalR is something completely different. SignalR supports two way HTTP(S) requests using web sockets. WCF supports all sorts of communication (through configuration), like HTTP(S), pipes, SOAP, and can, in theory, be used on any host (IIS/WAS, Windows Service, do we have any other flavors?). Please correct me if I'm wrong.
Read my (free) ebook Object-Oriented Programming in C# Succinctly. Visit my blog at Sander's bits - Writing the code you need. Or read my articles here on CodeProject.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
raddevus wrote:
It works well and is extremely easy to implement.
Easy you say. I recently picked up a copy of Programming WCF Services and I was suffering from information overload by the end of the first chapter. The shear volume of what can be done in WCF and granularity of the configuration settings can be a little overwhelming when looking at it for the first time. I myself thought that building a service application would be relatively easy until I started reading this book. Now I am a little apprehensive about taking the plunge without further study.
if (Object.DividedByZero == true) { Universe.Implode(); } Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
Foothill wrote:
I was suffering from information overload by the end of the first chapter
That's what I often dislike about books and what I try to avoid in my own writing. Why can't we start out making a really simple service (like the example you get when you create a new WCF project) and go from there? Nowhere along the way should you feel overwhelmed. In fact, you should feel like the book (or blog) just gave you enough information to confidently start experimenting on your own! Explain something like Miffy[^] would do without losing any depth on the subject!
Read my (free) ebook Object-Oriented Programming in C# Succinctly. Visit my blog at Sander's bits - Writing the code you need. Or read my articles here on CodeProject.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
i see a lot of blog posts around the internet that says WCF is Dead, any other thoughts?
I just created a whole new WCF service in the past few weeks. Seemed pretty much alive to me :)
Read my (free) ebook Object-Oriented Programming in C# Succinctly. Visit my blog at Sander's bits - Writing the code you need. Or read my articles here on CodeProject.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
As far as I know SignalR is something completely different. SignalR supports two way HTTP(S) requests using web sockets. WCF supports all sorts of communication (through configuration), like HTTP(S), pipes, SOAP, and can, in theory, be used on any host (IIS/WAS, Windows Service, do we have any other flavors?). Please correct me if I'm wrong.
Read my (free) ebook Object-Oriented Programming in C# Succinctly. Visit my blog at Sander's bits - Writing the code you need. Or read my articles here on CodeProject.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
I bought a book on it.[^] I'm about half way through it. It uses the best method it can to maintain a connection, based on that platform you're running it on. Web Sockets is one. I'm a fan of WCF, but it can be a real PITA to configure. What I like about SignalR over WCF is that it's stupid simple to set up and maintain.
If it's not broken, fix it until it is
-
Foothill wrote:
I was suffering from information overload by the end of the first chapter
That's what I often dislike about books and what I try to avoid in my own writing. Why can't we start out making a really simple service (like the example you get when you create a new WCF project) and go from there? Nowhere along the way should you feel overwhelmed. In fact, you should feel like the book (or blog) just gave you enough information to confidently start experimenting on your own! Explain something like Miffy[^] would do without losing any depth on the subject!
Read my (free) ebook Object-Oriented Programming in C# Succinctly. Visit my blog at Sander's bits - Writing the code you need. Or read my articles here on CodeProject.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
I was kind of hoping for it to start with: here is the absolute minimum you need for a WCF service to run; now let's show you all the fun things you can do. Alas, the book reads more like technical documentation. If I wanted a sleep aid, I would browse over to the RFC standards archives. I find the text for RFC 822 especially riveting X| ;P
if (Object.DividedByZero == true) { Universe.Implode(); } Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
