Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I need to have HTTP server embedded in my .NET application. Simply, there will be two dynamically generated views, but one can said – there will be just two different pages. Is it worth to use WCF as presented in blog post: Building a Basic Web Server Using WCF for such a simple task? Would it be just easier and better in this case to use HttpListener class?
WCF’s strength is to serve data to a lot of different clients in a lot of different formats. If this is just going to be a simple web page and the browser is the only client, I would say that WCF is not worth it. ASMX is much simpler and easy to use. WCF is supposed to be the way of the future but that doesnt mean ASMX is totally useless yet.
I have never used the HttpListener class so unfortunately I can’t comment on if it is a good idea or not.