The curse of the never-ending async method call

Posted by: More Whidbey stuff, on 17 Dec 2014 | View original | Bookmarked: 0 time(s)

Whether you use promises, callbacks, or other abstractions (except maybe the async/await pattern) to deal with asynchrony, control flow is going to get harder to follow. Stack traces are typically meaningless, and finding what went wrong can take substantially more time. One thing that very often goes wrong, especially during development, is when an asynchronous method never calls back. It may be because a service never answers, or because theres a bug in the code that causes the callback to never...

Category: Debugger | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 649 | Hits: 18

Similar Posts

  • Dynamic in C# 4.0: Creating Wrappers with DynamicObject more
  • How To Cache Rows In DevExpress ASP.NET GridView more
  • Take Two: A jQuery WCF/ASMX ServiceProxy Client more
  • Fun With Method Missing and C# 4 more
  • Demeter Transmogrifiers To The Rescue more
  • Exception Handling Advice for ASP.NET Web Applications more
  • AJAX Logging with Exponential Backoff more
  • The MethodLinq concept more
  • Minimizing unit Test Fragility 8 features in Typemock Isolator to help more
  • Escalating an AudioVideoCall to a conference in UCMA 2.0 more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD