I am .net developer from India. Self learned. Mostly focused on Web and API development. Now looking for next job change. Have very little knowledge in WPF and zero knowledge in WCF.
I recently visited other job posting sites [https://www.naukri.com/ | https://in.indeed.com/] and job hunters looking for a developer who have experience in WPF, WCF, SignalR, Blazor, Asp.net webforms, .net core mvc, API development plus TypeScript and Angular and Whatnot.
Now the question is as a developer should I have to learn all of it. Thank you in advance.
WCF looks to be dead actually. It is not supported in .Net Core yet so I do not believe it has sense to learn.
There’s an ongoing .net core port though it’s not a 1 to 1 port. It’s funded by .net foundation and the main developer seems to be from WCF as well. It looks interesting on how it’ll grow from there as it’s a ground up rewrite and we have some legacy systems here that might be able to move to .Net Core if it takes off. Though I agree it’s probably not something you’d want to learn these days, not until CoreWCF improves from just being focused on SOAP.
This is totally optional, however as you are more focused on the ‘backend’ of .NET and services. I would recommend learning WCF. As WPF, this is a UI framework using xaml.
I wanted to expand on this aswell as it will change depending on the developer path you want to pick. When it comes to jobs, the normal options for web are;
Full stack, know a front-end and backend technology/language(s)
front-end very specialized in everything front-end.
backend very specialized in everything backend.
As you are job hunting, look around for the most used technology around your area and try taking advantage of that.
Do not be discouraged or feel worried when companies list lots of technologies and languages you need to know for X job. Most of the time it’s HR listing them.
WCF, no. It’s kinda dead.
WPF can be a very useful thing to know.
Learn the things you need to get the job you want. In the case of WCF, it’s legacy at this point and most companies are not building new solutions with WCF. You’d be better learning ASP.NET.
In regards to WPF, you’d also be better off learning Xamarin.Forms as it seems to be getting the most attention for .NET 6.
WCF is ChannelFactory – Binding – Endpoint. That’s basically all you have to know.
WPF is basically what web development should have been. All the XAML is just .NET code expressed as XML.
Oooo, there’s a fight happening outside. I may continue later.
C# devs
null reference exceptions