As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I want to write webservice on .NET (my Client can be Android, iOS, Mac OS, Website...). My question is that I should use WCF or ASP.NET to do this?
I assume you mean ASP.net Web Apis when you mention ASP.net. There is also ASP.net soap services but those won't be ideal to work with on platforms such as android or iOS.
If you are unsure about what the different web services are, you will most likely want to use ASP.net Web APIs as these are easy to set up and offer multiple content types, XML, JSON, possibly more...
WCF is more built for web services however it has a steep learning curve, which is why I say if you're unsure about what you want, you most likely aren't making something which will require WCF.
For more information I suggest reading: http://idesign.net/articles/asp_net_web_api_vs_wcf.htm
I am assuming you are asking for WCF or websevice. I think WCF is better option. For your refrence:
http://www.thedevheaven.com/2012/10/difference-between-wcf-and-web-service.html
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I'm gonna start developing a single page web application using Microsoft stack. In some critical parts of the project I have to provide real time data.
I can use Signalr or Web Sockets for these kind of tasks. Can you do a comparison of them in terms of usability, performance or learning curves of these technologies. And I'm glad to know if you have another option to suggest.
Thanks in advance,
I think you should go with signalR. It is part of .net framework, it also supports web sockets and if any client doesnt support web sockets it will fallback to long-polling, forever frames any other technology available.
.NET 4.5 WebSockets vs SignalR
http://www.asp.net/vnext/overview/signalr/signalr-and-web-sockets
http://www.hanselman.com/blog/YourUsersDontCareIfYouUseWebSockets.aspx
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I would like to get some feedback from the asp.net community about the current technologies used in creating a new web service.
If i want to get started on exposing a web service that talks to oracle database and returns some results should i be leaning towards WCF web service or ASP.net Web API ? Which one is preferred?
Thanks in advance.
This question has been more or less answered here. I also really recommend that you take a look at this article.
But that being said, to keep it short, you can think of WebAPI as a simpler more lightweight alternative to WCF. WebAPI services operate over HTTP and are best suited to simpler tasks, whereas WCF is more versatile in the protocols that it can communicate with, and communicates using SOAP which in itself is a fairly heavyweight alternative to REST which is often used with WebAPI.
Since you are simply providing what is essentially a data access point, I would recommend that you go with WebAPI.
I assume you are talking about WCF Data Services.
Web API is much younger than WCF DS, and thus is a little less mature. Web API last I checked did not support full filtered queries (a la OData) outside of a pre-release.
http://nuget.org/packages/Microsoft.AspNet.WebApi.OData/0.3.0-rc
However its worth noting that Web API does look like its much more configurable.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
My application is built into WPF using Infragistics control(xaml).
I wanted to port the existing app into Web but we don't want to use silverlight(for silverlight we need plugin to be available in our browser and target users will not be having permission to install any plugin into their browser) is there any third part control available which helps us to port our WPF pages into WEB faster.
There are two ways to port WPF to web:
Silverlight (which you said you can't use) and
WPF XAML Browser Applications
Those are the only options I'm aware off.
If you want to convert your WPF app to ASP.NET Web forms or MVC you would have to do it manually.To make it easier you could create shared code which can be used by both WPF and the web application.
If you've followed the MVVM pattern in the WPF project that will make your job a lot easier as you can re-use the view model in MVC (with minor changes)
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
i have a general question. I want to develop a Web Application for business process modelling. The application was build using c# and WPF as Desktop Application Software and now i would like to develope it as Web Application. what technology should i choose?
I've tried to find it myself but there are many different opinions about that topic. Is there any general rule or methodology which can help me decide?
Your question is not quite constructive. You need to talk to some Architect to understand your business and the requirements to fill up the gaps of choosing a technology. It is quite vague to answer your question whether to choose ASP.NET webforms/MVC or probably a different platform than .NET to suit your needs.
On a general answer, if you are planning to port your whole application developed on desktop using WPF, you can consider porting to Silverlight which might cut down your cost to 90% (probably), where you will able to reuse all codes you have written so far. But that's totally your call and your business needs.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
What is REST service and how it is different from web service. thanks
In a nutshell, a REST service is focussed around resources. A SOAP service is typically focussed around operations.
Note that both REST and SOAP services are considered to be web services if they are operating over HTTP, even though different protocols are used.
See here for more info.
Infact you cannot compare between REST & Web Service, as Web service/ WCF service makes use of REST. For details please check below links
http://www.oracle.com/technetwork/articles/javase/index-137171.html
http://en.wikipedia.org/wiki/Representational_State_Transfer
You probably want to compare a RESTful web service with other web services. Check the link...
It's a way of designing a web service.
Representational State Transfer
it was asked before...
Difference between REST and WebServices
another one.
http://www.ibm.com/developerworks/webservices/library/ws-restful/
http://www.xfront.com/REST-Web-Services.html
http://www.ajaxonomy.com/2008/xml/web-services-part-1-soap-vs-rest