Migration to Microsoft .NET

Our methods of migration to Microsoft .NET are based on three pillars:

1. Experience. Groups of engineers and analysts with over 1000 hours of experience in the given technology, who research the source product. We have a successful track record of working with popular platforms, poorly documented solutions and with custom client implementations.

2. Tools. Migration tools and component libraries (objects, classes, tags, etc.) that facilitate migration.

   For example, typical components that are employed in migration projects are: DHTML ComboBox with dynamic lookup of values via Web Service, multi-column DropDown for .NET WinForms (similar to Access control), etc. DataArt invested several thousands of hours creating these custom components.

3. Customized approach. Migration is always performed by two teams that interact with the customer independently from one another. The first team consists of analysts and QA specialists. It is responsible for coordination and support of information and tools necessary to preserve 100% of useful functionality intact. The second team performs the implementation side of migration using an appropriate technique, for example adaptation, porting, or re-factoring.

Whenever possible and appropriate, we assure that the final product design allows for maximum utilization of the Microsoft .NET advantages:

1. Automated deployment from a Web-server, natural both for WebForms and for Windows Forms;

2. Availability of re-usable network APIs based on Web Services & remoting for features that are required by third-party applications;

3. Possibility of using Windows Forms in MDI and SDI Frameworks and on Web-pages (for integration with Web-portals) without any changes to the code;

4. Maximum usage of managed code and universal Microsoft .NET Framework features to simplify future integration with the new generation of Microsoft server platforms.

Working With Cutting-Edge Technologies

Historically, DataArt has been investing serious efforts in researching perspective technologies, experimenting with early software releases and maintaining leading-edge development practices. Early research is usually performed by analysts from a dedicated R&D group or through "pilot projects".

In a standard scenario, analysts evaluate the product's or platform's early pre-releases and provide their opinion on the following factors:

1. Advantages for potential users
2. Advantages in terms of lowering development costs or increased productivity
3. Optimization of deployment and operation phases
4. Costs involved with training, updating development infrastructure, toolsets, etc.
5. Existing vendor's programs supporting the new technology

Provided that the technology looks promising or there is a well-defined client interest, a "pilot project" is organized. The pilot project explores the technology further, with particular attention to:

1. Any specifics of development process associated with the new technology
2. Risks and constraints, probability of changes in the release version
3. Types of applications likely to benefit most from the use of new technology

Many of today's popular technologies have passed through this evaluation process and have been adapted for active use. Microsoft .NET framework itself has been tested through a series of pilot projects, before being selected as a primary development platform at DataArt.