.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

IIS 7.0: Extend Your WCF Services Beyond HTTP With WAS

Posted By:      Posted Date: August 21, 2010    Points: 0   Category :ASP.Net

Learn about a new IIS feature called the Windows Process Activation Service (WAS) that makes it possible to host Web services beyond HTTP.

Dominick Baier, Christian Weyer, and Steve Maine

MSDN Magazine September 2007

View Complete Post

More Related Resource Links

Web Services: Extend the ASP.NET WebMethod Framework with Business Rules Validation


In an earlier article the authors showed how to build a custom WebMethods extension that provides XML Schema validation, a function that is lacking in ASP.NET. In the process they established a foundation for enforcing business rules during the deserialization of XML data. The technique, which is described in this article, uses declarative XPath assertions to test business rule compliance.In building this business rules validation engine, the authors integrate the validation descriptions into the WSDL file that is automatically generated by the WebMethod infrastructure. Finally, they demonstrate how to extend wsdl.exe, the tool that generates WebMethod proxy/server code from WSDL files, to make use of their extensions.

Aaron Skonnard and Dan Sullivan

MSDN Magazine August 2003

Web Services: Extend the ASP.NET WebMethod Framework by Adding XML Schema Validation


WebMethods make the development of XML Web Services easier by encapsulating a good deal of functionality, but there is still a lot of underlying XML processing that you have to be responsible for. For example, WebMethods do not validate messages against the implied schema. Because they are not validated, the response that's returned can result in unintended consequences. To address this, the authors extend the WebMethod framework by adding XML Schema validation through a custom SoapExtension class.

Aaron Skonnard and Dan Sullivan

MSDN Magazine July 2003

HTTP 401: Unauthorized when trying to specify reporting services for integration, cannot connect to




I am trying to install reporting services and join it into existing service farm.

Main  MOSS 2007 is on one pc, with config bases etc, while reporting services, reporting services db will be on other pc. 

We are using same domain account to run sharepoint services and reporting services. 

I've installed web part of MOSS on that other computer, also reporting services and sql server, set reporting services in integration mode.

Either way, it wont work for me:


If i am running the service of reporting services as Network Service account, then the /reportserver page will complain about some generic error "probably you dont have access to the farm if you are in integrated mode" etc.... 

I've read that i should include networkservice into a group WSS_WPG which i did, no luck anyway, same error

If i try to type the adress into the integration with reporting services in moss admin page, i will get error like "expected xml received html" and alot of red text.


If i switch service to run from domain account (the one that is used for running sharepoint on the domain) (we did the spn thing, didnt work either), the /reportserver page will open

(moss2k7/ReportServer - /

Hosting WCF Services (NetTcp and WS-HTTP) on a windows MCSC fail over cluster

Hi I have a set of WCF Services that use the above protocols. How do i host these in a MCSC Cluster and expose them to the clients ? When hosting the service which is the IP i should use ? The Virtual IP of the Cluster ?

Reporting Services 2008: "HTTP status 401: Unauthorized" Issue


I'm getting the error "The request failed with HTTP status 401: Unauthorized" whenever I try to list the reports on my reporting server. The weird thing is, it works when I run the asp.net application on my dev machine hitting the server reporting services web service url (http://www.example.com/reports/reportservice2005.asmx?wsdl) but when the asp.net app is installed on the server (running iis 7) hitting the same url I get the error. Here's my set up:


SQL Server Reporting services 2008 (not R2)

Web service url: http://www.example.com/reports/reportservice2005.asmx?wsdl


Created a proxy ReportingServices2005.cs

Web.config has <identity impersonate="true"/>

Code to list reports:

<asp:ListView ID="lvReportList" runat="server">
            <asp:PlaceHolder runat="server" ID="itemPlaceholder"></asp:PlaceHolder>
            <asp:HyperLink runat="server" ID="hpReportLink" NavigateUrl='<%#Eval("Url")%>'><%#Eval("Name")%></asp:HyperLin

REST and http services


Hi All,

Can all services that are non-SOAP, be deemed as RESTful? Where can I get some indepth information on the same?



Does SSL activation in Reporting Services 2005 exclude the use of http in favor of https ?


Hello SSRS Community,

I would like to know if the activation of SSL (Secure Socket Layer) allow the use of both HTTP and HTTPS to access the report server

I have been asked by a web developer in my company to check if in SQL Server 2005 reporting services the activation SSL makes it possible to access the Report Server with both HTTP and HTTPS.
For example:
1. Without SSL activation you can use http://ServerName/ReportServer to access your report server
2. Once SSL is activated, we are wondering if it will be possible to access the Report Server with the following two links:
a. https//ServerName:443/ReportServer

Thank you


EndPointNotFoundException was caught: "There was no endpoint listening at http://xxxx/xxx/Services/M


When I using a windows service call WCF service, exception happened.

There was no endpoint listening at http://xxxx/xxx/Services/MyService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

I have tried http://xxxx/xxx/Services/MyService.svc from url and it is shows its WSDL.

The WCF service in another domain, local machine who invoke web service is Win7, and service is win8.

Following is my configuration:


      <binding name="BasicHttpBinding_IFqlService" maxBufferSize="2147483647" maxReceivedMessageSize="2147483647" receiveTimeout="00:05:00" sendTimeout="00:05:00" closeTimeout="00:05:00"> 
      <security mode="TransportCredentialOnly"> 
        <transport clientCredentialType="Windows">
          <extendedProtectionPolicy policyEnforcement="Never" />       
      <readerQuotas maxArrayLength="2147483647"/>      
      <binding n

New IQueryable Support for Http Services in WCF


One of the things that caught my attention when WCF Data Service was released a couple of years ago was the ability of using URI segments for passing queries directly to an underline linq provider. This represented a very powerful feature for allowing clients to filter and manipulate a large data result set on the server side with a simple API and without incurring in any unnecessary performance penalty (the queries are performed and resolved in the data source itself most of the times) and having all that logic implemented in the service itself.

I've always thought that this cool feature should be something that anyone could reuse in any service, and not something available in WCF data services only. For example, If you already had an existing REST service implementation, moving that logic to a WCF data service with OData support was only the option you had if you wanted to reuse that query support.  By moving your service to a WCF Data Service, you were also limiting your service to the content types supported by OData (Xml Atom and JSON), and it would only makes sense with services centered around the concepts of CRUD for manipulating data.

Fortunately, this functionality has been moved to a separated library and released as part of the new WCF Web APIs in wcf.codeplex.com. This means that you can now use the IQ

Versioning REST Services with WCF Http Processors


As I discussed in my last post, the new WCF Http Model includes http processors that you can use to inject cross cutting aspects into an existing service. We can use processors for supporting a versioning schema based on content types as it discussed here by Peter Williams. 

Supporting custom media types in a WCF Http Service is a now a piece of cake with the new MediaTypeProcessor. The only thing you need to do is to implement a new processor by deriving your  class from the base class MediaTypeProcessor or any existing implementation like XmlProcessor for example.

The implementation I showed below derives from the XmlProcessor implementation and adds support for two new content types ("application/vnd.mycompany.myapp+xml" and "application/vnd.mycompany.myapp-v2+xml")

extend wcf Authentication Services.


in .net 3.5 Microsoft has introduced Applicaton Service through WCF. This includes Authentication Service, Role Provider Service and Profiler Service. Now I am having a requirement that force me to add one more Function in AuthenticationService class. But I have found that AuthenticationService Class have no public Constructor. Thus it cannot be inherited. So is there any other way, I can add one more function into System.Web.ApplicationServices.AuthenticationService class.


FYI. Extention Methods doesnt work in this scenario.
- Regards,
Bhagyesh Joshi, India.

Installing and Uninstalling Services

Installing and Uninstalling Services.Unlike most projects you create in Visual Studio .NET, Windows Service projects cannot be run directly from the development environment by pressing F5. This is because the service in the project must be installed before the project can run.

You can quickly install your service application by using a command line utility called InstallUtil.exe.

Getting Started with Windows SharePoint Services

Of all of the capabilities of SharePoint, I thought I would start with the most basic installation - as a corporate intranet. It is likely that we will need to discuss some of the elements of SharePoint as we go along, so this also gives us the opportunity to review these elements for future reference.

Before going into too much detail, I would like to point out that you can try the core SharePoint framework (known as Windows SharePoint Services or WSS) for free. On Microsoft's Web site you can download a trial version of Virtual PC 2004 (VPC). Using VPC, you can install the Windows 2003 Evaluation Kit and the WSS add-on. This combination will give you 45 days to evaluate the setup.

Building a Searchable Phone Directory with Windows SharePoint Services

I want to continue to build out the intranet site we've started in our previous articles. A standard item in every intranet is a staff/employee list. Most companies implementing Windows SharePoint Services (WSS) are large enough to have a database that contains all employees. We will use the aggregation features of SharePoint to include data from this database into our intranet.

ASP.NET Architecture - ASP.NET Worker Process - HTTP Pipleline - Http Modules and Handlers

"ASP.NET is a powerful platform for building Web applications, that provides a tremendous amount of flexibility and power for building just about any kind of Web application. Most people are familiar only with the high level frameworks like WebForms and WebServices which sit at the very top level of the ASP.NET hierarchy. In this article I'll describe the lower level aspects of ASP.NET and explain how requests move from Web Server to the ASP.NET runtime and then through the ASP.NET Http Pipeline to process requests.

Building a 3-Tier App with Silverlight 3, .NET RIA Services, and Azure Table Storage

Silverlight 3, .NET RIA Services, and Windows Azure Services Platform makes a 3-tier Cloud application easier to build: Silverlight 3 as presentation tier, .NET RIA services as the business logic and data access tier, and Windows Azure Table as the data storage tier. The sample application in this article demonstrates the architecture with a simple Survey application with all these technologies working together from Windows Azure.

New Features in Windows SharePoint Services 3.0

Windows SharePoint Services 3.0 (WSS 3.0) is the next version of WSS 2.0, released on 2007, and Microsoft Office SharePoint Server 2007 (MOSS 2007) is built on top of this. Windows SharePoint Services 3.0 takes full advantage of Microsoft ASP.NET 2.0 and the core Microsoft .NET 2.0 runtime. WSS 3.0 offers a lot of new features and programmability support. I have consolidated a list of new features and enhancements in the below section:
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend