"Just to add my two cents to the discussion, my team (and a couple of others I know) have been using regions heavily to further structure the code. But the usage of region is like other code practices: it depends on the project team, company, etc.
So definitively, the possibility to keep the existing regions would be great (if not, it would break the existing code organisation)."
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Since NArrange now provides compatibility with the StyleCop ordering rules, this feature may have a lower priority. Custom regions of members would likely not adhere to StyleCop rules, which NArrange will be promoting moving forward.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1964306
Originator: YES
Chris on CodeProject adds:
"Just to add my two cents to the discussion, my team (and a couple of others I know) have been using regions heavily to further structure the code. But the usage of region is like other code practices: it depends on the project team, company, etc.
So definitively, the possibility to keep the existing regions would be great (if not, it would break the existing code organisation)."
Logged In: YES
user_id=1964306
Originator: YES
Bob Mottram adds:
"Nice work. Is there any possibility of preserving existing regioning in the code?"
Logged In: YES
user_id=1964306
Originator: YES
Since NArrange now provides compatibility with the StyleCop ordering rules, this feature may have a lower priority. Custom regions of members would likely not adhere to StyleCop rules, which NArrange will be promoting moving forward.