Old way: you need a custom localization infrastructure, which means writing tedious code. Custom infrastructures are further hampered by the inability of non-programmers to provide localization support to development teams.
XAF way: built-in localization that integrates with the standard .NET approach and supports runtime customizations and online translation services is included.
|