tag:blogger.com,1999:blog-6082652835152798567.post6452498312030388387..comments2024-03-28T00:58:12.736-07:00Comments on Sql server, .net and c# video tutorial: Part 19 - Creating and throwing strongly typed SOAP faultsUnknownnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6082652835152798567.post-71604610742063492592017-04-06T07:50:03.550-07:002017-04-06T07:50:03.550-07:00try this one will help you
catch (FaultException...<br /><br /><br />try this one will help you<br /><br /><br />catch (FaultException ex)<br /> {<br /> DivideByZeroFault lDivideByZeroFault = new DivideByZeroFault();<br /> lDivideByZeroFault.Error = ex.Message;<br /> lDivideByZeroFault.Details = "Denominator cannot be ZERO";<br /> throw new FaultException(lDivideByZeroFault);<br /> }Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6082652835152798567.post-34714321130634811502014-12-19T09:44:41.864-08:002014-12-19T09:44:41.864-08:00I receive error stating, "The creator of this...I receive error stating, "The creator of this fault did not specify a Reason". Should I add FaultReason parameter to the FaultException method? Even after adding it, I still get an error as, "FaultException`1 was unhandled by user code". Anonymousnoreply@blogger.com