Vote for a new WCF Client code generator

Hello All

I've recently learned that Microsoft is currently working on building a WCF Client code generator for .NET Core VB.NET projects. The generator was originally included for C# projects, but so far not for VB.NET. It seems we're about to see that change (ETA unknown).

Here's the initial problem report:

https://developercommunity.visualstu...sual-/10525581

...and here's the GitHub issue on the subject, complete with a link to the active pull request by Carol Wang [MFST]:

https://github.com/dotnet/wcf/issues/4381

I'd like to encourage all of my fellow VB.NET developers to upvote the GitHub issue (the first entry, by Charles Monk), and also to comment, so as to assist the team in gauging community interest.

WCF remains a fabulous tool; it's still a mystery to me how it could have been so easily supplanted by so primitive a technology as REST. And now that we have CoreWCF for the server side, the package is complete (mission statement notwithstanding).

Make sure to vote, and thank you for your attention on this matter.

Thanks,
Jeff Bowman
Fairbanks, Alaska

Personally , if we are talking on the plain goo ol' WCF web service, I would have downvoted and would have gone every day with a different profile and downvote again and again (if I cared).
I have worked extensively in the past previous years with WCF and I come to conclude that it is the worst thing ever happened to mankind. All the bindings and the mex and the configuration hell and not supporting unknown types and need to rebind again and again was a nightmare. I will never use it for a newer app. I have only one app left with it at the office , got rid of it everywhere and I just leave that app to show the hell you have to go through for anyone that might have the bright idea to use it.....Fortunately we only have admins and a know it all supervisor but he does not even know (and gladly) what WCF is. And it stand for Worst Creativity Fart.

Quote:

---

Originally Posted by sapator

... what WCF is. And it stand for Worst Creativity Fart.

---

:eek::bigyello:

Quote:

---

Originally Posted by sapator

Personally , if we are talking on the plain goo ol' WCF web service, I would have downvoted and would have gone every day with a different profile and downvote again and again (if I cared).
I have worked extensively in the past previous years with WCF and I come to conclude that it is the worst thing ever happened to mankind. All the bindings and the mex and the configuration hell and not supporting unknown types and need to rebind again and again was a nightmare. I will never use it for a newer app. I have only one app left with it at the office , got rid of it everywhere and I just leave that app to show the hell you have to go through for anyone that might have the bright idea to use it.....Fortunately we only have admins and a know it all supervisor but he does not even know (and gladly) what WCF is. And it stand for Worst Creativity Fart.

---

Okaaayy... :ehh:

My experience with it has been only limited, in comparison. I haven't gone much further than BasicHttpBinding; that's served all of my needs quite well so far.

Its two main advantages are, in my opinion, as compared with REST:

• Self-definition, enabling client code generation
• Its implementation of WS-Discovery

I never ran into even a hint of the problems you're describing. I do all of my configurations in code, not declaratively—I find the latter to be cumbersome and obscure (and not resuable). I did encounter some mex complications initially, yes, but once I got that all worked out and my code base put into a private NuGet package I never had to touch it again. My implementations worked flawlessly.

But again, I do concede that my point of view is from the base of the lighthouse, not the top.

Given these two important advantages, and assuming simple needs, it's still worth voting for IMO.