The .NET Framework did not provide any built-in functionality for creating or consuming syndication feeds until version 3.5 with the introduction of the
System.ServiceModel.Syndication namespace. The most germane class in this namespace is SyndicationFeed. As you can probably guess from its name, this class represents a syndication feed. It has properties like
Copyright, which provide details about the feed. The content items that make up the feed are specified via the
Items property, which is a collection of SyndicationItem objects. The
SyndicationFeed class also has a static
Load method that parses and loads the information from a specified RSS 2.0 or Atom 1.0 syndication feed.
In addition to the
SyndicationItem classes, the
System.ServiceModel.Syndication namespace also includes two formatter classes, Atom10FeedFormatter and Rss20FeedFormatter. These classes take a
SyndicationFeed object and generate the corresponding XML content that conforms to either the Atom 1.0 or RSS 2.0 specificiations.
More… How to create a syndication feed for your website
- Visual Studio Project Templates
- REST Singleton Service produces a service that exposes the full HTTP interface (GET, POST, PUT, and DELETE) around a singleton resource, and it automatically provides both XML and JSON representations for the underlying resource.
- REST Collection Service similar to the REST Singleton Service only it also provides support for managing a collection of SampleItem resources.
- HTTP Plain XML Service provides ONLY the GET and POST operations for those who don’t care about fully conforming to the RESTful design and would rather build a REST/RPC hybrid service by overloading GET and POST using the HTTP Headers.
- Atom Feed Service template provides a sample implementation that shows how to programmatically generate and return a SyndicationFeed instance.
- Atom Publishing Protocol Service template produces a full-fledged AtomPub service capable of managing collections of resources as well as media entries.
- WebProtocolException allows you to directly set your HTTP status code.
- WebServiceHost2/WebServiceHost2Factory which provides a zero-config experience. Provide support for Help Page.
- Help Page and using [WebHelp] for annotation. Simply navigate to /help
- Added Extension methods to the WebOperationContext class.
You can download the WCF REST Starter Kit here.
For samples of using the starter kit, look at this A Developer Guide to the WCF REST Starter Kit.
ASP.NET provides application services on the Web that enable client applications to access user authentication, role, and profile information. This information can be accessed by client applications that are written in different languages and that run on different operating systems. The only requirement is that these clients be able to communicate through SOAP 1.1 protocol.
This walkthrough is divided into the following parts:
Part 1 shows how to configure an ASP.NET Web site (Web Application and WCF Web Service) to expose the application services.
Part 2 shows how to build a Windows console application that accesses a user’s authentication, roles, and profile information. In this walkthrough you will build a Windows console application, but the ASP.NET application services are available to client applications that run on any operating system.
Mapping and Configuring the Application Services
Before you can access the user’s credential and profile information from the client, you must create mapping files – WCF service file (.svc) that point to the application services. This makes the services available to any application that is running on any platform that can send and receive messages in SOAP format. You must also configure the Web site so the application services are exposed on the network
Walkthrough: Using ASP.NET Application Services
IIS supports specifying multiple IIS bindings per site, which results in multiple base addresses per scheme. A WCF service hosted under a site allows binding to only one baseAddress per scheme.
So if you get an error like this “This collection already contains an address with scheme http wcf”, you may want to look at the following:
Solution in .Net Fx 3.0:Supporting Multiple IIS Bindings Per Site
Solution in .Net Fx3.5: BaseAddressPrefixFilters
Via TopXML : How can WCF support multiple IIS Binding specified per site in WSCF/WCF