Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 298 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
A .Net automation - exception pass-through
xo
Member Posts: 34
The automation is a POP3/SMTP mailcomponent that just sends and receives mails. I've safeguarded all entrypoints from Navision by catching Exception at the top-level of every called method, and I'm using "using", to ensure disposing resources. Also a try-catch guarded destructor that disposes a socket is there.
But now the curious thing. The mail component has a class with two private methods - these two methods are the only ones that are not guarded by try-catch - as they aren't supposed to be called from Navision. But still, I've found out that in these two methods is the only place where the exception I'm getting is thrown that shows up in Navision. I can't explain why that is.
But now the curious thing. The mail component has a class with two private methods - these two methods are the only ones that are not guarded by try-catch - as they aren't supposed to be called from Navision. But still, I've found out that in these two methods is the only place where the exception I'm getting is thrown that shows up in Navision. I can't explain why that is.
0
Comments
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
Follow up. It turns out that the error was in fact just Exception.Message mirrored via ERROR in Navision so it looked like the exception passed through when in reality it was just a logged exception. Sorry about that.
Nothing more to see.