begin_end_sequence
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| begin_end_sequence [2018/03/21 04:50] – created wolfgangriedmann | begin_end_sequence [2019/08/29 17:57] (current) – wolfgangriedmann | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| So, if you are transporting VO code, you can keep these statements safely, but for new code please use the .NET equivalents [[trycatch|Try - Catch]]. | So, if you are transporting VO code, you can keep these statements safely, but for new code please use the .NET equivalents [[trycatch|Try - Catch]]. | ||
| Where the X# compiler adds functionality in the translation is in the recover statement, to support the VO '' | Where the X# compiler adds functionality in the translation is in the recover statement, to support the VO '' | ||
| + | Please see here for a detailled explanation: | ||
| The biggest difference between the error handling in .NET and Visual Objects stays in the ErrorBlock() handling. Please see the relative topic: [[vo_errorblock|The VO ErrorBlock]] | The biggest difference between the error handling in .NET and Visual Objects stays in the ErrorBlock() handling. Please see the relative topic: [[vo_errorblock|The VO ErrorBlock]] | ||
| + | The biggest difference is that in VO you can set a global error handler, and this is then called every time a runtime error is encountered, | ||
| + | |||
| + | In .NET, if an exception is occurring, and there is no '' | ||
| + | |||
| + | Therefore, in X# the presence of error handling is much more important than in VO. | ||
begin_end_sequence.1521607800.txt.gz · Last modified: 2018/03/21 04:50 by wolfgangriedmann