web

You’re offline. This is a read only version of the page.

News and Announcements icon

Dynamics 365 CommunityForums Microsoft Dynamics AX (Archived) ax 2009 - best practic...

Microsoft Dynamics AX (Archived)

ax 2009 - best practice for try+catch block

(0) Share

Report

Report

Posted on by Community Member

Hello,

I have try + catch block.

The catch should be empty - what is the best practice way doing that?

try {

// my code ...

} catch {

// do nothing.

}

Thanks :)

*This post is locked for comments

I have the same question (0)

All responses Img

All responses (5)

Answers Img

Answers (0)

Suggested answer

StevenK on at

Like (0)

Report

Well having an empty catch statement wouldn't be best practice, but if you're going to do it then

try

{

// do something

}

catch

{}

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Well - this is not best practice.

I know that there is a way putting something instead of {} - I just forgot that ...

What shall I put instead of catch {} ?

Thanks :)

Was this reply helpful? Yes No
Suggested answer

Daniel Weichsel on at

Like (0)

Report

The best practice is to call exceptionTextFallThrough() in the catch block -- and of course document the reason why nothing is done.

Was this reply helpful? Yes No
PopCola 5 on at

Like (0)

Report

Hi, I'm currently migrating to X++ language from other .net PL. I'm kinda curious if the "finally" block is also available in X++. Is it? Thanks!

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

Hi POPCOLA,

There is no finally statement in X++.

Please review following link

msdn.microsoft.com/.../aa893385.aspx

Please verify, and let us know your findings

Was this reply helpful? Yes No

Helpful resources

Quick Links

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1

Martin Dráb 4 Most Valuable Professional

#1

#3

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans