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
  • Folder structure
  • Generating .zip file

Was this helpful?

  1. Issues and Troubleshooting

Assessment Report Issue

PreviousShort-Circuit Boolean Logic in C#NextKnowledge Base

Last updated 1 year ago

Was this helpful?

VBUC has an option called Assessment, which creates a report used as input to estimate the possible effort required for the migration process. (For more information, see )

The process itself is not complicated; however, the generated files should respect the required structure since any modification (adding, deleting, or modifying folders or files) can affect any other tasks that may be carried out during the migration process.

Folder structure

Keeping the files in the correct folder hierarchy is essential for a correct analysis process. Please do not add, delete, or modify any folder or file.

The following folder structure must be maintained.

  • Assessment: The main directory where all files are stored.

  • DependenctGraph: Folder that contains .csv files.

  • HTMLReports: Folder that contains html, css files and images.

  • <file>.xml: All necessary XML files generated by the assessment process.

  • <file>.fgp: Fingerprint file.

Generating .zip file

If you need a .zip file for a process, first verify that the files generated by the assessment are similar to those in the previous section.

Once you have verified the assessment folder has no issues, compress it to a .zip file from the Assessment folder.

Verify that the Assessment .zip file contains the Assessment folder.

Assessment Process