Custom Support
Our core competency is helping teams learn to use gmStudio and using gmStudio to develop Upgrade Solutions for others. Our participation in your effort can dramatically accelerate your progress and reduce risks.
Watch this brief video presenting typical Custom Support engagement:
Custom Upgrade Features
Section titled “Custom Upgrade Features”In custom support engagements, we often go beyond “fixing what breaks” and focus on shaping the upgraded solution into something teams can confidently maintain and extend.
Structural Upgrades
Section titled “Structural Upgrades”That typically starts with structural improvements—consolidating shared files to eliminate duplication, removing dead or obsolete code that no longer serves a purpose, and thoughtfully integrating any hand-written code into the upgrade system so it takes advantage of your prior work and conforms to you existing standards and conventions rather than creating and exception.
COM API Replacements
Section titled “COM API Replacements”One of the most important technical requirements for VB6/ASP legacy modernization is dealing with upgrading COM libraries and controls with .NET replacements. This is one of the most important and powerful features of the gmStudio platform and out methodology and services address it in a flexible and comprehensive way.
Resolving Language Incompatabilties
Section titled “Resolving Language Incompatabilties”The VB6 and ASP languages have many subtle and important differences from C# and http://VB.NET, and language and runtime compatibility issues can surface when older patterns meet modern frameworks. The gmStudio translation engine understands these challenges and addresses most of them in general right out of the box. But, real world systems often have unique quirks and problems that require something more specialized at scale. Customer Upgrade solutions will often include special various optimizations that go beyond the standard translations and implement unique solutions to language translation problems. In the same phase, we often implement organizational coding conventions and carry out targeted refactoring to improve clarity, consistency, and long-term supportability—without changing intended behavior.
Win32 API Rework
Section titled “Win32 API Rework”We also tackle lower-level dependencies that can become obstacles in a modern environment, such as legacy entry-point (Win32) API calls. Replacing these with safer, more maintainable alternatives helps reduce operational risk and improves portability across contemporary Windows configurations.
Value Added Features
Section titled “Value Added Features”Many engagements also include value-add enhancements that leave the solution stronger than where it started. Common examples include:
- adopting strongly typed generic collections
- evolving application architecture to better align with modern practices,
- establishing custom coding standards for consistency across teams, and
- incorporating DevOps conventions so the upgraded system is easier to build, validate, support, and deploy in a repeatable way.
Please contact us to discuss your requirements and learn about options.