|
Kevin Marois wrote: I've been looking into SignalR
SignalR is very interesting.
|
|
|
|
|
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.
|
|
|
|
|
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
|
|
|
|
|
Nice, seems SignalR does more than I thought.
Going to check it out for sure
|
|
|
|
|
Yup but still I think, WCF vs SignalR is not the right comparison to do. WCF is the bigger brother. It's a platform. A platform that's getting eclipsed by the recent Asp.net MVC Web APIs. Sadly WCF would fade out from so many day-to-day applications.
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy.
|
|
|
|
|
Sander Rossel wrote: and can, in theory, be used on any host (IIS/WAS, Windows Service, do we have any other flavors?).
Selfhosted.
|
|
|
|
|
Absolutely, much less named pipes and many different forms of authentication.
WCF is a bit like XML or Microsoft Office. It can do sooooo much more than most people realize or what most people use it for. When you need it, it's really nice, but often difficult to learn and master.
I've been hearing people calling RoR and jQuery dead, but I still find myself using jQuery once in a while.
|
|
|
|
|
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).
|
|
|
|
|
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 
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.
|
|
|
|
|
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!
|
|
|
|
|
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  
if (Object.DividedByZero == true) { Universe.Implode(); }
Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
|
|
|
|
|
Oh! That looks interzzzzzz...
|
|
|
|
|
Does it matter? You can still use it.
|
|
|
|
|
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.
|
|
|
|
|
Fifteen years ago I saw similar posts about VB6.
Check out the VB.NET forum 
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
I just created a whole new WCF service in the past few weeks.
Seemed pretty much alive to me 
|
|
|
|
|
Who told you? The management, the tech team. Or you just heard it. I suspect the former one.
|
|
|
|
|
Dead in many ways. Alive in few ways.
Dead - The world has moved away from SOA-WebServices-XML-UDDI etc. Which was like prime for WCF.
With Web-API-JSON, it's ultra quick and development ease is like amazing.
Asp.net MVC based API has brought things to super cool level. You can , so damn easily manage your URL paths based on different needs, with the "the controllers/actions" in MVC. It's just out of the box. It's highly salable, maintenance , deployment everything is so easy.
And mind you, I remember the days, I had spent hours and hours fiddling with issue in Windows Phone Client WCF Async Proxy code. It just sucked like hell. Such a simple thing goes screwed. MS tools were so stupid for the job.
Everything is out now. Web-API just made it so lightly coupled. You care a damn about where the services are hosted. No proxy generation , nothing is required. And you can switch between any stack as you want. The client just needs to get updated about the service URL changes.
We can do all these in WCF, by patching up the code, but it doesn't look so pro. And guess what, Microsoft is not going to support WCF for REST model. We just hit the wall there.
For most of the daily application needs, all we need is just Client-Server model that sends Data. Web-API-JSON combo just fits the need for most of these. So WCF would be dead here in all these.
But if you want to go for advanced Customized Network components, WCF is still there. You can fiddle with all Binding, Security, endpoints, etc etc. There are a pile of things you can configure.
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy.
|
|
|
|
|
Vunic wrote: And guess what, Microsoft is not going to support WCF for REST model.
Just implemented that last month. It wasn't the easiest (as with anything WCF), and I would probably use Web Api next time instead, but it works.
|
|
|
|
|
The MS folks (Who are in touch with us consulting things) , themselves recommended to move out of WCF long ago saying anything related to REST, will not be updated on WCF. WebAPI is the new way!. So we cleaned up our circus of REST on WCF and moved to WebAPI. You would love it! WebAPI is super cool and simple, for all the basic data transactions it's just more than enough!
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy.
|
|
|
|
|
Ok, then I'll do that instead next time.
|
|
|
|
|
Gabriel Sas wrote: any other thoughts?
Do penguins have knees? 
Seriously, I have heard no such thing, so I wonder if it isn't just idle speculation??? On the other hand, the death of Silverlight also came as a huge surprise to me, so what the heck do I know?
Gabriel Sas wrote: C# WCF Dead or alive?
It must be alive, otherwise someone would have written a RIP post here in the Lounge 
Anything that is unrelated to elephants is irrelephant
Anonymous
-
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-
I'd just like a chance to prove that money can't make me happy.
Me, all the time
|
|
|
|
|
I don't think it is dead just set aside. Who knows it may come back when people decide to use it more than it is being used these days.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
