Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K 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
- 304 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
.net interop exceptions
Bgestel
Member Posts: 136
considder the following in a nav 2013 situation
if ListofFiles.find('-') then
repeat
Xmldoc.Load(ListofFiles.Path);
until ListofFiles.next = 0;
Where Xmldoc is System.Xml.XmlDocument.'System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
and let's assume this is an unattended process running on a nas service tier.
In the good old days, the xml document automation would return true or false to signal if something went wrong in the import. .net will throw an exception an Nav has no clue what just happened and rolles back the transaction.
To work arround this :
- i could wrap the if codeunit.run constraction arround the .net xml assembly
-> I dont like this approach because it produces spagetti code
- i cook my own custom xml assembly , doing the trying and catching and translating it to a true / false return
-> I dont like this approach because it will increase maintenance and introduce deployment dependencies
- Ms development could provide some serious exception handling syntax to nav to complete the .net interop.
-> sounds great.
Does annyone have other smart idea's to work arround this ??
if ListofFiles.find('-') then
repeat
Xmldoc.Load(ListofFiles.Path);
until ListofFiles.next = 0;
Where Xmldoc is System.Xml.XmlDocument.'System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
and let's assume this is an unattended process running on a nas service tier.
In the good old days, the xml document automation would return true or false to signal if something went wrong in the import. .net will throw an exception an Nav has no clue what just happened and rolles back the transaction.
To work arround this :
- i could wrap the if codeunit.run constraction arround the .net xml assembly
-> I dont like this approach because it produces spagetti code
- i cook my own custom xml assembly , doing the trying and catching and translating it to a true / false return
-> I dont like this approach because it will increase maintenance and introduce deployment dependencies
- Ms development could provide some serious exception handling syntax to nav to complete the .net interop.
-> sounds great.
Does annyone have other smart idea's to work arround this ??
**********************
** SI ** Bert Van Gestel **
**********************
** SI ** Bert Van Gestel **
**********************
0