Dear Firefly Community Member,
Often when we review new code written by developers after the migration, we see that they are working too hard doing things in new code that were only relevant for migrated code.
When writing new code, you can write shorter code that is easier to maintain - since you don't have to bother with all the extreme use cases that the migrated code bothers with.
A simple example is calling the "MarkParameterColumns" method. Don't use it in new code :)
The only thing this method does is make sure that if you use VarName on a column that was sent to it, it'll return 'Parameter.ColumnName' and not 'Variable.ColumnName'
This is important for migrated code since we can't anticipate where you've used VarName - but is never relevant for new code.
In the interest of making the most of .NET and developing faster and more effectively in .NET we've created (and reorganized lately) the two most important sections for developers after the migration in our documentation web site:
Common migrated code patterns and how to improve on them in new code in NET
n this section we've covered common code patterns that were used in magic or in the migrated code and that can be written a lot simpler in the migrated code.
Read the section
Specifically, we've added two articles:
Simplify Incoming Parameters
Stop using CustomCommands and Handlers for Buttons
And have improved the Replace Inner Classes With Entity Method article
Refactoring Migrated Code
In this series of videos and articles, we review the most basic refactorings that any developer should start doing as soon as you gain some confidence in the code.
Read the section
Note that the first 7 articles in this section are basic, and after that, the complexity rises
Join our User Group
Let us know if you found these articles useful or have any suggestions/questions. Please join our user group, Migrated by Firefly where all new articles are first posted and questions and discussion around the migrated code are discussed.
|
