Team Developer to .NET: Migration vs. Porting
Why Application Migration Beats Porting?
The Answer: True .NET Code
The two options for transitioning to .NET are Migration and Porting. In the migration approach, the goal is to adapt the application into the .NET environment. This involves adopting as many .NET programming conventions and techniques as possible without compromising the compatibility of the application. And this allows .NET programmers to take over the maintenance of the converted code.
In porting, the structure and programming conventions of the original environment are kept and the conversion is limited primarily to syntax. In the porting approach, the application relies on a runtime environment that emulates the original programming environment. This makes it difficult to use standard .NET data types, components and techniques after porting. Therefore the porting approach is mainly useful for "throw-away code" and applications that need to run in the .NET environment, but will be maintained in the original language.
Rapid .NET Applications
Composer Sabertooth creates production-ready .NET applications:
- Uses native .NET types
- Access Levels are inferred
- Object-Method syntax makes your code more Object-Oriented
- .NET Events, not Messages
- Choose between VB.NET & C#
Complete migration to .NET results in a mainstream environment with a choice of developers and third-party tools. Porting locks organizations into a proprietary environment.
Benefits of Unify’s Composer Sabertooth Migration Approach:
- Code can be maintained by .NET programmers
- Standard .NET data types, components and techniques can be used to maintain code
- Greater use of standard .NET data types
- Use of event handling rather than messaging
- Increased object orientation
- Access Levels set to the most restrictive level rather than setting all Access Levels to "Public"
- No vendor lock-in as 100% of the source code is provided, including the component libraries
- Reports converted to Crystal