.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

FaultContract - can I use non soap fault messages

Posted By:      Posted Date: September 01, 2010    Points: 0   Category :WCF
I want to use the FaultContract functionality for reporting errors but I want to completely define the message on the wire (as I do in the MessageContract) - I do NOT want the message to appear as a soap fault on the wire.  Is that possible?  I guess what I really want is for a contract to have two possible results, the normal successful result and a specialist exception result.  This is for something to go through an XML guard and a soap fault doesn't meet the IDL spec.   I'd be grateful for any pointers   Thanks

View Complete Post

More Related Resource Links

MSMQ and .NET: Send MSMQ Messages Securely Across the Internet with HTTP and SOAP


When creating a distributed system you frequently need to provide for communication between two entities that are not in sync. Microsoft Message Queue Server (MSMQ) provides the kind of store-and-forward messaging in a pre-built infrastructure that can help you address these kinds of messaging needs. In the past, MSMQ was accessed using a COM wrapper. Now there's a .NET wrapper that lets you accomplish your messaging goals easily from your Framework-based code. To illustrate the use of the wrapper, the author builds a messaging application, sends MSMQ messages over the Web, and discusses messaging security.

David S. Platt

MSDN Magazine December 2003

House of Web Services: Accessing Raw SOAP Messages in ASP.NET Web Services


Web Services exchange XML messages. Most of today's Web Service toolkits do their best to hide this fact from developers, by exposing a Web Service's behavior as method invocations against objects instead.

Tim Ewald

MSDN Magazine March 2003

DIME: Sending Files, Attachments, and SOAP Messages Via Direct Internet Message Encapsulation


Direct Internet Message Encapsulation (DIME) is a new specification for sending and receiving SOAP messages along with additional attachments, like binary files, XML fragments, and even other SOAP messages, using standard transport protocols like HTTP. In this article, the author explains what DIME is and how it differs from MIME encapsulation. A detailed description of the message format and how it is parsed, as well as working with SOAP and extending it with WSDL, is also included.

Jeannine Hall Gailey

MSDN Magazine December 2002

ASMX web service soap fault

Hi,I have a ASMX web service, and as I understand the ASMX services does not include soap fault details in the WSDL.Thus, I have changed the generated WSDL to include soap fault.Will this cause any error in the endpoint systems?Regards, 

How to pass response or fault soap message to other end point using WCF?


I have changed the ReplyTo and FaultTo of SOAP Message Headers in WCF ,

and I d like  the response message can be sent to other service endpoint,

I tested it,But Response Message could not be sent to other service.

How can I make it?

Thanks in advance.


Frank Xu Lei--????,????
Focus on Distributed Applications Development and EAI based on .NET




Signing SOAP Messages with Certificates in WCF

Let me preface this question by saying that I am a novice with WCF--especially configuration.

I currently have a .NET client written that uses WSE 2.0 to consume a web service provided by a 3rd party. The web service is designed to accept a signed SOAP message for login. Signing is achieved via a purchased certificate. Once authenticated, the service returns a SAML assertion token which is included on subsequent messages until the client calls a logout method on the web service. I was hoping to convert this client to WCF for hopefully better tracing capabilities and because it is tedious installing WSE 2.0 on target machines. I also am hoping to avoid forthcoming obsolescence of WSE.

Here are the details of the web service. Please let me know if something is lacking.

The service uses SOAP 1.1 with attachments for communication. The login messages must be signed with the purchased certificate. The public key for the certificate has already been supplied to the service provider. The endpoint addresses actually specify "https", which I understand to mean that the communication is happening over SSL--this is one area that I am a bit hazy on, so please forgive me if I stated that incorrectly. The service uses WS-Security as a means of securing the message.

In what I've tested so far, I have been able t

How to create a WCF service that is in compliance with Soap Messages with Attachments

Hi, I know that there are many ways to send attachments, but unfortunately i need to create a webservice that follows the "SOAP messages with Attachments" specification (http://www.w3.org/TR/SOAP-attachments). This specification can be sumarrizing as and Multipart MIME message that groups a Soap Envelope and more files as attachmens in differnent MIME parts, such as SOAP with Attachments MIME envelope -Root Body MIME part --Soap Envelope ---Soap Header ---Soap Body - Mime Part 2 --First File - Mime part 3 --Second File .... Hopefully that structure can be helpful,otherwise you can easily check in the specification page. I don't know how to do that: - Creating a Contract with one parameter that will a Message that will encapsules all the information, but this means that I need to create all the MIME parts manually. and lqater in the client I'll have to split the information and deserialized in objects. Any help would be great, Thanks in advance for your help. Cheers

User messages without hard coding


Hi All,


How to manage user messages to avoid hardcoding messages accross the web application.





.Net Frameword 4 SOAP Web Service



We want to upgrade from VS2005 to VS2010. Before we do that, I would like some clarity about some things.


Can we build typical SOAP webservices with the 4 Framework as I could with 2.0?


Would a WCF Service allow me to have both REST/SOAP services in one application?


Is Framework 4 ONLY for REST services and I need to stick to 3.5 for SOAP?


I downloaded the free Web Developer 2010, but I cannot seem to get anywhere trying to figure this out.


Thanks for any input.





Test Run: Fault Injection Testing with TestApi


Fault injection testing is the process of deliberately inserting an error into an application to determine whether it deals with the error properly. We'll explain how you can introduce faults into .NET applications at run time using the Managed Code Fault Injection APIs of the TestApi library

James McCaffrey

MSDN Magazine August 2010

Test Run: Testing Silverlight Apps Using Messages


Silverlight greatly simplifies the process of building rich Web applications, and we'll walk through an example of using Messages as a quick method of interactively testing simple Silverlight apps.

James McCaffrey

MSDN Magazine March 2010

The Polyglot Programmer: Concurrency with Channels, Domains and Messages


Axum is not a general-purpose language like C# or VB, but one aimed squarely at the problem of concurrency, designed from the outset to be part of a suite of languages that collectively cooperate to solve a business problem.

Ted Neward

MSDN Magazine September 2009

Data Points: Data Performance and Fault Strategies in Silverlight 3


In this month's column, the author shows how binary encoding works, the effect it has on an application's performance, and how it behaves by demonstrating it in action.

John Papa

MSDN Magazine August 2009

.NET Matters: Handling Messages in Console Apps


Many developers who use the Microsoft .NET Framework think that application type is tied to the libraries that can be used in that application. Stephen Toub clarifies.

Stephen Toub

MSDN Magazine June 2007

Service Station: WSE 3.0, SOAP Transports, and More


It's that time again. Time to answer some of the questions I get on a regular basis. This month I'll look at service orientation and policy-based compatibility, SOAP's transport-neutral design, and Web Services Enhancements (WSE) 3.0.

Aaron Skonnard

MSDN Magazine June 2006

Mobility: Add Keyboard Support to Compact Framework Apps by Trapping Windows Messages


The Compact Framework Control class doesn't provide direct access to Windows messages. However, with P/Invoke, a few lines of native code, and the Compact Framework MessageWindow class, it's still possible to access underlying Windows messages. This can be used to work around any .NET Framework features, including keyboard support, that are not included in the Compact Framework.

Alan Pulliam

MSDN Magazine April 2004

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