VBUC Documentation | Mobilize.Net
Mobilize.NetForumsBlogDocumentation Home
  • Mobilize.Net VBUC
  • Introduction
  • Install and Licenses
  • Get Started
  • Migration Guide
  • VBUC Features
  • Mappings Grammar
  • Generated Code
  • Upgrade Options
    • Data Access
    • Grids
    • Microsoft
    • Sheridan
    • Others
    • Code Conversion
    • C# Features
  • Third-party controls
  • Best Practices
  • EWIs
    • Warnings
    • Issues
    • ToDos
    • Notes
  • Issues and Troubleshooting
    • Microsoft.VisualBasic Uses
    • Safe and Unsafe Methods Layer
    • Third Party Components
    • Migration Process
    • Classic ADO Conversion to ADO.NET
    • VB6 and .NET integer division
    • VB6 On Error Statements
    • Running a .NET Core application in a machine with no Visual Studio installed
    • Databases issues
    • Unsupported assemblies on .NET Core and .NET 5
    • Icon Extraction Issues
    • HTTPS sites are not loaded in Windows XP
    • Short-Circuit Boolean Logic in C#
    • Assessment Report Issue
  • Knowledge Base
    • FAQ
      • Does the VBUC support the Sheridan VB 6.0 controls suit?
      • How effective is the Visual Basic Upgrade Companion tool at converting an application's front end?
      • What controls does the Visual Basic Upgrade Companion tool supports?
      • How does the VBUC handle VB6 Collections?
      • Can the VBUC migrate intrinsic VB6 functions and libraries?
      • Where is the source code for the support (helper) classes used by the VBUC?
      • How does the VBUC convert ADO to ADO.NET?
      • Can the Visual Basic Upgrade Companion tool be customized?
      • What are Stubs?
    • How-To
      • App.Config and Database Access
      • Avoid reflection in Hot Paths
      • Convert ESRI ArcGIS Visual Basic 6.0 applications to .NET
      • Drag and Drop Conversion Steps
      • Inserting elements in a ListView
      • String vs StringBuilder
      • Word Automation in VB6 vs .NET
      • Configure default Factory Database provider
      • GetPrivateProfileString Windows API working in migrated code
      • Upgrade projects with shared files
  • Release Notes
Powered by GitBook
On this page

Was this helpful?

  1. Knowledge Base
  2. FAQ

Does the VBUC support the Sheridan VB 6.0 controls suit?

The Visual Basic Upgrade Companion can convert many of these controls to .NET native components, using the equivalency shown in the table below. Non-supported controls can be accessed through COM interoperability without problems, but Mobilize can also customize the VBUC to generate the desired mappings to inherent .NET components or other 3rd party libraries.

Troubleshooting/solution

Control

Supported

Equivalent

SSFrame

Yes

System.Windows.Forms.GroupBox

SSPanel

Yes

System.Windows.Forms.Panel

SSOption

Yes

System.Windows.Forms.RadioButton

SSCheck

Yes

System.Windows.Forms.CheckBox

SSCommand

Yes

System.Windows.Forms.Button

SSTree

Yes

System.Windows.Forms.TreeView

SSMonth

Yes

System.Windows.Forms.MonthCalendar

SSYear

Yes

System.Windows.Forms.MonthCalendar

SSDateCombo

Yes

System.Windows.Forms.DateTimePicker

SSDBCombo

Yes

Infragistics.Win.UltraWinGrid.UltraCombo

SSDropDown

Yes

Infragistics.Win.UltraWinGrid.UltraDropDown

SSDBGrid

Yes

Infragistics.Win.UltraWinGrid.UltraGrid

SSIndexTab

Yes

System.Windows.Forms.TabControl

SSSplitter

Yes

System.Windows.Forms.SpplitterPanel

SSListBar

Yes

Infragistics.Win.UltraWinListBar.UltraListBar

For more information see Third-party controls

PreviousFAQNextHow effective is the Visual Basic Upgrade Companion tool at converting an application's front end?

Last updated 2 years ago

Was this helpful?