/
Great Migrations FAQs
Great Migrations FAQs
Search FAQs
- Support Statement: Surface Pattern Syntax
- Support Statement: Steps for Developing an ASP Site Upgrade
- Support Statement: Building gmStudio Extensions using gmAPI and .NET
- Support Statement: Overcome the Limits of AI for Large Scale Software Modernization
- Support Statement: gmSL to move a variable declaration
- Support Statement: Partial Translations
- Support Statement: Override a routine in authortext.gmsl
- Support Statement: Stub Replacement
- Support Statement: How many programmers?
- Support Statement: Consolidating Shared Code Files
- Support Statement: gmStudio Licenses
- Support Statement: Unused Symbol Analysis and Reporting
- Support Statement: Useful Search reporting patterns
- Support Statement: What is the meaning of Translation Status = SUCCESS?
- Support Statement: using specializedHookup="on" when migrating event handlers
- Support Statement: What does migStatus="external" stand for
- Support Statement: Using gmSL to determine if an optional argument was omitted
- Support Statement: ListView.Add example of using gmSL to map COM to .NET
- Support Statement: Generating a Global Stub Framework
- Support Statement: How does gmStudio run builds?
- Support Statement: Removing Code
- Support Statement: Translation Challenges
- Support Statement: Setting Scope for an ASP Site Upgrade
- Support Statement: MigrationSupport (gmRTL) Source Code
- Support Statement: Removing a container control (e.g. vsElastic )
- Support Statement: Improving Type Inference for MSHTML
- Support Statement: Sample Migration of CommonDialog to Winforms
- Support Statement: Upgrading a COM Component property to a WinForms Static property
- Support Statement: Dealing with Twips to Pixels
- Support Statement: GlobalSettings enhancements
- Support Statement: Deprecating MigrationSupport namespaces
- Support Statement: Translating Client-Side VBScript and VBS files
- Support Statement: Using a Custom Visual Studio Version (or SDK tools)
- Support Statement: Setting Platform for builds
- Support Statement: Consolidating COM API versions
- Support Statement: Type Inference Limitations
- Support Statement: Target Architecture Changes
- Support Statement: Dealing with DataEnvironment / DataReport
- Support Statement: Using gmSL for deep migrations
- Support Statement: Remove tasks from a project that do not match any entry in an "include list"
- Support Statement: Custom Build Order
- Support Statement: License Activation
- Support Statement: How can I automatically edit a VBP file?
- Support Statement: msxml2 versioned progIDs
- Support Statement: Upgrading VB6 Error Handling for C#
- Support Statement: Cleanup VB6 Source Directory
- Support Statement: missing IDF for mscoree.dll
- Support Statement: How to selectively suppress OptionalArguments=on for a specific method
- Support Statement: adding/removing Stub Framework Content
- Support Statement: Using GlobalIncludes
- Support Statement: Using a gmAPI executable with gmStudio
- Support Statement: Dealing with Difficult GoSub migrations
- Support Statement: What is a Build-Complete ASP Upgrade?
- Support Statement: Suppress .NET Compiler warnings
- Support Statement: Form uses stub controls and Designer Crashes
- Support Statement: fixtype for type=VBS class in a #include
- Support Statement: gmSL EditSource
- Support Statement: Migrate Form_Load as event handler
- Support Statement: Remove Application Function and Replace Calls
- Support Statement: updating (of ignoring) a custom meta-language file during translation
- Support Statement: Dealing with "bad" code
- Support Statement: Retaining Short in a COM API
- Support Statement: Migration DLLs
- Support Statement: ADO to ADO.NET?
- Support Statement: Reducing Late Calls, CallByName/dynamic
- Support Statetment: ReplaceFile for Stubs
- Support Statetment: ReplaceFile for AppObject
- Support Statement: Automated Testing
- Support Statement: Helping with resolving a Build Error
- Support Statement: Unable to open language file <..\usr\VB7lang.vbi>
- Support Statement: Apply PreEdits using gmsl
- Support Statement: Dump Source Code from a VBI file
- Support Statement: Local Migration to remove an argument from calls
- Support Statement: add a gmSL routine to a translation script
- Support Statement: Integrated Build
- Support Statement: hybrid upgrade of Toolbar.Buttons.Add to WinForms extension
- Support Statement: "Unexpected" gmAPI Behavior
- Support Statement: Making an Upgrade Unit Test
- Support Statement: Proprietary Designers (e.g. ActiveReports)
- Support Statement: .NET Build Standards, Framework, Core, and Common
- Support Statement: What happened to my filenames?
- Support Statement: Twips to Pixels
- Support Statement: IDFs for interop assemblies
- Support Statement: Dealing with symbol case changes
- Support Statement: How to get the list of COM interfaces implemented by a COM class
- Support Statement: Modifying VB6 Source Files
- Support Statement: Dealing with Source Code Changes
- Support Statement: Running a specific gmStudio other than the installed version
- Support Statement: Setting Up IDFs
- Support Statement: Microsoft Access Applications
- Support Statement: VBA Applications
- Support Statement: Designer Control GUID
- Support Statement: gmSL Handlers and Commands
- Support Statement: Making a new Metalang File
- Support Statement: Large Sample
- Support Statement: VS Version Selection
- Support Statement: VB6 Refactoring
- Support Statement: VB6 Forms Upgrade Strategy
- Support Statement: System Metalanguage Files
- Support Statement: Modifying the migration of a VB6 Intrinsic Function (e.g., Split)
- Support Statement: Dealing with multi-dimensional Arrays
- Support Statement: Running and Comparing results for a test code
- Support Statement: Techniques for Weak Typing and ref Tempargs
- Support Statement: gmBasic Script Parameter Replacement
- Support Statement: Making a control into a class
- Support Statement: Dealing with TypeLib Alias
- Support Statement: Dealing with name clashes in COM stub classes
- Support Statement: Dealing with multiple versions of the same class in IDF
- Support Statement: Dealing with Library/Class Name Clash
- Support Statement: Refactor Remove, Reauthor and Spec codes
- Support Statement: Duplicate COM symbols in different TypeLibs
- Support Statement: What is an easy COM replacement?
- Support Statement: Reference is not open
- Support Statement: Office Upgrade
- Support Statement: oo40 to Oracle Data Provider for .NET
- Support Statement: Type Inference and Type Replacement
- Support Statement: Verifying a Migration Solution
- Support Statement: Unit Testing MigrationSupport.DataLib
- Support Statement: Upgrading .NET interop dependencies
- Support Statement: DataLib
- Support Statement: Using str.Length instead of str.Len()
, multiple selections available,
Related content
Partnering with Great Migrations
Partnering with Great Migrations
More like this
Great Migrations Documentation Home
Great Migrations Documentation Home
More like this
Client List
Client List
More like this
Videos
Videos
More like this
Our Partner Program
Our Partner Program
More like this
gmniMigration -- Deprecated
gmniMigration -- Deprecated
More like this