deploy: 552e37fedc
This commit is contained in:
parent
c736753393
commit
3941105a09
398 changed files with 49386 additions and 129 deletions
|
|
@ -0,0 +1,2 @@
|
|||
<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>NET Exception Handling in CAL on BC AL Help</title><link>https://microsoft.github.io/bcalhelp/navpatterns/1-patterns/net-exception-handling-in-cal/</link><description>Recent content in NET Exception Handling in CAL on BC AL Help</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><atom:link href="https://microsoft.github.io/bcalhelp/navpatterns/1-patterns/net-exception-handling-in-cal/index.xml" rel="self" type="application/rss+xml"/><item><title>TryFunction NET Exception Handling in CAL</title><link>https://microsoft.github.io/bcalhelp/navpatterns/1-patterns/net-exception-handling-in-cal/tryfunction-net-exception-handling-in-cal/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://microsoft.github.io/bcalhelp/navpatterns/1-patterns/net-exception-handling-in-cal/tryfunction-net-exception-handling-in-cal/</guid><description>Originally by Mostafa Balat, Microsoft Development Center Copenhagen
|
||||
Abstract When there is a need to use .NET classes within C/AL, one of the main challenges is to handle the exceptions the methods of these .NET classes may throw. Eventually, if not handled, they will basically bubble up as runtime errors, halting the current operation a user is doing without having a chance to properly display errors in a user-friendly format.</description></item></channel></rss>
|
||||
Loading…
Add table
Add a link
Reference in a new issue