Click here to Skip to main content
15,886,422 members
Please Sign up or sign in to vote.
1.00/5 (3 votes)
See more:
I am working on Asp.net 3.0 from 1.5 Years, I want to learn diff. technology. So, Which do you prefer? I am looking for MVC or WCF. Please suggest one to me?
Posted
Updated 13-Feb-13 9:03am
v2
Comments
Guirec 13-Feb-13 1:14am    
In my opinion there is no contest: I vote for MVC.
The fundamentals of a protocol agnostic service mechanism (WCF) is very interesting in theroy but in reality it is a pain in the neck (debugging and configuration) for almost every user. Many architecs are reverting from it now in favor of home made API or technology like WebAPI.
MVC will serve you more on your resume.
Sergey Alexandrovich Kryukov 13-Feb-13 1:18am    
Not a correct question, nearly off-topic. Nobody can give a valid answer, because we don't know your background and criteria...
—SA
ZurdoDev 13-Feb-13 15:40pm    
OP is just looking for opinions.
Sergey Alexandrovich Kryukov 13-Feb-13 15:47pm    
I do understand that, but an opinion not based on some knowledge about OP is not so valuable... And MVC and WCF cannot be considered as alternatives...
—SA
db7uk 13-Feb-13 15:15pm    
As SA said. You cannot get an answer without background. As for the first comment. You can't go MVC if you are talking about service bus's, tcp and socket communications or anything real time. my opinion is that MVC (more to the point WebAPI that was spawned from MVC and MVC not being a service anyway its a pattern) is for websites. WCF is for complex services. WebAPI is for http based services that compliment http based UI's.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900