Home/ Questions/Q 4536626
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T14:33:42+00:00

I’ve been a .NET guy from the get go in my career, but within

  • 0

I’ve been a .NET guy from the get go in my career, but within my work experience I have yet to venture out into the world of WCF or MVC. I think the difference is more framework / convention based with respect to WCF and MFC, correct me if I’m wrong.

But, what I’m really wondering is this: Is it correct to say that WCF is to MVC as the regular ASP.NET WebServices are to the regular ASP.NET Web Apps? As in, WCF and MVC should be used together and regular ASP.NET WebServices and regular ASP.NET Web Apps should be used together? Or is it ok to intermix any combination of the 4?

Also, why would one not want to upgrade to WCF and / or MVC?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    MVC is a convention based approach to ASP.NET web apps. I think you are correct there.

    That analogy does not hold between ASP.NET web services and WCF, IMO.

    Both ASP.NET web services and WCF are convention based programming paradigms. For e.g. both frameworks will match your SOAP call to a method implementation based on the name. Both will serialize data in the payload to your object model based on structure and field names, etc.

    WCF provides a unified programming model for different transport types – TCP, named pipes, MSMQ, HTTP etc. It gives you more control over how your service is hosted. It gives you more control over how the payload is encoded.

    I think it would be more accurate to say that WCF is a unification of .NET Remoting and ASP.NET WebServices, with great improvements in extension points.

    Hope this helps.

    • 0