8 Articles match "Throw"

89 Articles match "Throw"

• The Best from DevelopMentor

  MORE

• Workflow 4 and soap faults
  
  Throwing a FaultException When a FaultException is thrown in a workflow service pretty much the expected thing is done. With this second SendReply activity, creating and throwing a FaultException the workflow looks like this: With the following expression used to initialize the fault. Not really surprising as we throw an error that is never caught and terminates the workflow. So all I needed to do is remove the Throw activity and let the second SendReply do its work. Image by ponChiang via Flickr Note: This blog post is written using the.NET framework 4.0 Enjoy!
  The Problem Solver - Wednesday, March 24, 2010
  READ MORE
• Marshalling native function pointers
  
  throw gcnew OutOfMemoryException("Could not allocate memory on C++ free store"); }. throw gcnew OutOfMemoryException("Could not allocate memory on C++ free store"); }. Now that the book is written and all urgent tasks I had to defer due to the book are done, I find some time to blog about technical topics. Recently, a customer asked me how to marshal function pointers across managed / unmanaged interop boundaries. If you know a simple API and two attributes and if you are aware of a pitfall specific to marshaling function pointers, the job can be quite easy. of the CLR.
  Marcus' Blog - Friday, April 6, 2007
  READ MORE
• WF4&WCF and message correlation
  
  Should I change the Id the WorkflowServiceHost would try and find an existing workflow with the changed person Id, fail and throw a FaultException with message “The requested operation could not complete because instance key '4d7e998a-4cff-4743-3dd4-2afd5578383c' could not be found.”. In the previous blog posts, here , here and here , I demonstrated how to use WCF from WF4. This same some more about sending multiple messages to the same workflow, AKA Workflow Correlation. Fortunately the WF4 story is much better. Much better! So the regular client has hardly any changes. Enjoy!
  The Problem Solver - Wednesday, September 2, 2009
  READ MORE
• Keeping things safe wth AsyncCallback
  
  What happens if DoWork throws an exception? The async delegate infrastructure will conveniently cache the exception and re-throw it when I call EndInvoke. The.NET Async pattern is a very neat way of running functionality asynchronously. The async pattern is where for a synchronous method DoWork be have a pair of methods BeginDoWork and EndDoWork to handle running the DoWork functionality on the threadpool. Now it is well documented that if I call the Begin method I must also call the End method to allow the async infrastructure to clean up resources it may have acquired. try. {.
  .NET Meanderings - Wednesday, March 18, 2009
  READ MORE
• Another reason for not using C# lock keyword
  
  So assuming your scoped code runs correctly to completion or throws an exception the monitor is always recovered. The C# keyword at first glance looks like a real god send…since lock( myLock ) { // Critical code } Generates an “exception proof acquisition and release of the monitor, saving you from having to write Monitor.Enter(myLock); try { // Critical code } finally { Monitor.Exit(myLock) } So here at DM we have preached for the last few years how evil the C# lock keyword is. The first case no real problem…but with the second case there could be issues.
  .NET Mutterings - Sunday, October 8, 2006
  READ MORE
• Error handling in a NativeActivity
  
  quot; }, new Throw { Exception = new InArgument (ctx => new DivideByZeroException()) }, new WriteLine { Text = "End inner sequence." Note: This blog post is written using the.NET framework 4.0 RC 1 Using Workflow Foundation 4 the NativeActivity is the powerhouse when it comes to building native activities. One of its many capabilities is around error handling. Every so often I run into one of these things where things don’t quite work the way I expect them to and this is one of these cases. The basics of error handling when scheduling child activities. Activities =. {.
  The Problem Solver - Tuesday, February 9, 2010
  READ MORE
• Article: Avoiding 5 Common Pitfalls in Unit Testing
  
  IsValidForMask(Mask, path)) { throw new Exception(String.Format( "Invalid Path '{0}' for Mask '{1}'", path, Mask)); } } internal static bool IsValidForMask(String mask, String path) { mask = mask.Replace(".", ".").Replace("*", regex.IsMatch(path)) { throw new Exception(String.Format("Invalid Path '{0}' for Mask '{1}'", path, Mask)); } } }. Llewellyn Falco and I recently wrote an article for DevelopMentor's Developments newsletter entitled Avoiding 5 Common Pitfalls in Unit Testing. You can read it at the DevelopMentor website: [link]. I've republished here for my readers. Enjoy!
  Michael C. Kennedy's Weblog - Thursday, August 6, 2009
  READ MORE