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.
Can any one suggest me a good book for .Net Web Services beginers (C#)
Try this book, very highly recommended and current
ASP.NET 4 in C# and VB.NET
If you're looking for WCF, this one is great:
Essential WCF
If you're only just starting to do web services, I would strongly recommend you go and check out WCF. It's the current and future standard for communications between machines - web services and a lot more.
The book I always recommend to get up and running in WCF quickly is Learning WCF by Michele Leroux Bustamante. She covers all the necessary topics, and in a very understandable and approachable way. This will teach you everything - basics, intermediate topics, security, transaction control and so forth - that you need to know to write high quality, useful WCF services.
The more advanced topics and more in-depth look at WCF will be covered by Programming WCF Services by Juval Lowy. He really dives into all technical details and topics and presents "the bible" for WCF programming. He just recently completed a third edition, which covers WCF in .NET 4 and AppFabric and the Azure Service Bus, too.
If you are referring to WCF services then I would recommend the following book
Programming WCF Services, Third Edition
Mastering WCF and the Azure AppFabric Service Bus
ByJuval Lowy
http://oreilly.com/catalog/9780596805494/
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 10 years ago.
I am currently doing c#.net development and I wanted to create a webservice that would work with both my web app and my iphone app. I would ideally like to work with JSON. Is there any good guides out there that would help me build a good scalable web service using WCF? I don't currently have the funds to buy a book so I was hoping a set of online guides could get me to the level of understanding to start coding. Thanks!
I would use WebAPI, the former WCF WebAPI.
Now a part of Microsoft MVC.
Try it!
Loads of online ressources :-)
You can start here : http://www.asp.net/web-api
Basicly; you get a easy-to-use REST API for web applications without the hassle of WCF-configuration.
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.
we got a server at my job (windows server 2003 with sql server 2005)
Now i need to deploy a web service that will be consume in a iPhone application...
I am very new to .net and i really don't know how to set this web service online.
I have created a asp.net web service c# app and i want it to be accessible remotely so i can consume it thought my iPhone app. If you have any tutorial or tricks to do this! Help. Thanks
Here are couple of tutorials:
For SOAP Services
For Rest Service
Both of these use JSON for data and use a third party library like JSONKit, since native iPhone libraries don't have JSON support.
Edit:
As #MishieMoo mentioned iOS 5 built-in api supports JSON. For completeness I have added link to iOS5 tutorial.
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 have a web portal and the web portal has web services API.
Which solution would be best and why?
Should I....
1) Run the web portal and the web portal API on the same server or
2) Run the web portal and the web portal API on separate servers
It's all a matter of trading off different forces, there just can't be the same answer for everybody.
Here's a few things to consider:
Having the UI (portal) and it's dependent services on the same box makes for a very clear set of dependencies, when diagnosing problems you've got just one place to look. You can scale by adding more such boxes, each being self-contained. Clarity has a lot of operational value.
But, it's likely that the portal or the services will have different resource requirements, hence you are scaling (say) the portal when the services are not using much resource. Hence you have more copies of something portal or service than you strictly need. This may have considerable costs. Examples:
Licence costs. Suppose you have 10 copies of portal but really only needed 5, then that's 5 licences wasted.
Memory consumption. Suppose there's a fixed overhead in getting the services (or portal) up irrespective of load demands (think caching or database connections) then you are paying that cost for the un-needed instances
Back-end costs. Your services may connect to enterprise systems, eg a database. Each connection costs resources on the back-end. If you have un-needed instances you pay needless costs.
3.Platform tuning. You may need to tune the platform differently for your portal and the services. This issue is more noticable when considering whether to co-locate the database too.
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 11 years ago.
I need to develop WCF services for an application of mine. I am aware of web service concepts and know how to develop them using Java. Now i need to develop .net based WCF services. I know bits n pieces of .Net. Please guide me to some good tutorials for developing WCF services.
There is a getting started tutorial on WCF over at MSDN. You might want to check it out.
Other than that, overviews and what-have-you can be found on the WCF page in MSDN.
While there's always MSDN to quickly get you started, if you have the time to read a book Programming WCF Services by Juval Lowy is a really good in depth resource.
There are two good posts for quick start:
Writing the WCF Hello World App.
Writing your first WCF client.
And of course MSDN tutorial.
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 12 years ago.
I'm amazed that years over years IT pretend to simplify communication or software design and a few years later it declare it was over-engineered. EJB, SOAP, so looking at all the WCF stuffs do we as users (not as Microsoft or IBM who need to sell new stuffs) really need it ?
Update: this is a concrete example
http://www.go4answers.com/Example/expert-interoperability-issues-ws-736.aspx
The guy knows how to call a server with WS-Security using old soap and in WCF it seems it doesn't really help and worst it seems even more complicated as it is said:
"WCF has still some limitation - not all WS-Security configuration are possible without custom development."
Nobody seems to be able to have found a solution.
So can people instead of mere opinions give concrete examples (with source code both in wcf and in soap or rest for comparison) of hard problems (and not easy problems) that can be solved by WCF more easily than can be with traditional soap ?
What I like about WCF is that it can be as simple or as complex as you want it to be. I also really appreciate the separation between contract and binding, where you can clearly define your operations and have the option of choosing which transport to use.
WCF is meant to make a developer's life easier. You can re-write the logic for a service, auto-wire multiple endpoints, and voila...your logic is available via SOAP, REST, Named Pipes, etc.
Unfortunately it's not as easy as it was all made to sound. Personally, though, I still find it a useful tool for re-using my code.
If you really want to jump on the bandwagon and say that REST/JSON is the only way to go...then WCF will definitely seem over-engineered. ASP.NET MVC does a great job at RESTful JSON services if you don't want to deal with the WCF overhead.
With 4.0, they've simplified configuration. I find it very easy to do this. But realize WCF is designed to make a lot of the internals of communication between services transparent. You don't care if its SOAP, REST, etc. All you do is write your service and "hook them up". COde for my services is exactly like I'd write normal code, with the exception of a couple of attributes added to the class and methods and some configuration (with 4.0, very simple imho)