Sorry... things happen damn slow in ERP industry. Be glad at least it's not COBOL...
(Are you sure you really need it? In Navision one rarely writes big functions or classes where it would be useful. A typical customization rarely uses more than one level of hieararchy, I mean functios are generally directly called from OnRun or whatever and usually don't call other things.)
Do It Yourself is they key. Standard code might work - your code surely works.
Hi Shenpen
Thank your four your posting.
Comming from the Java / C# enviroment to Navision I sometimes miss some features
I will "do it myself". We are trying to use elements from Unified Process as our Navision Development process (Use Case driven development). This means that we will be "visiting" the same code unit multiple times as we iterate the development - and as a consequense introduce bugs in already working code. Unit testing is a "tool" to catch the newly introduced bugs.
Comments
(Are you sure you really need it? In Navision one rarely writes big functions or classes where it would be useful. A typical customization rarely uses more than one level of hieararchy, I mean functios are generally directly called from OnRun or whatever and usually don't call other things.)
Do It Yourself is they key. Standard code might work - your code surely works.
Thank your four your posting.
Comming from the Java / C# enviroment to Navision I sometimes miss some features
I will "do it myself". We are trying to use elements from Unified Process as our Navision Development process (Use Case driven development). This means that we will be "visiting" the same code unit multiple times as we iterate the development - and as a consequense introduce bugs in already working code. Unit testing is a "tool" to catch the newly introduced bugs.