Project Analyzer

VB.NET compatibility report – PicInfo sample application

Evaluation of the work required to upgrade this system to Visual Basic .NET.

Upgrade readiness

This project has no known serious upgrade incompatibilities. You may consider the upgrade.
It is recommended that you fix some issues before loading the system in VB.NET.

Evaluation of upgrade work

Type of issue Issues † Issues/file
Fix recommended before upgrade 1 0 0,2
Can be fixed before or after upgrade 4 0 0,8
Work required after upgrade 3 0 0,6
Total 8 0 1,6
       
Number of source files 5    
Number of forms 1    
Lines of code (LLOC) 371    
- in dead procs (certain, unexposed) 11    
- in dead procs (uncertain, exposed) 2    

†: Issues with dead code that could potentially be removed before upgrade.

Number of upgrade issues by file

Work recommended before upg NoUpg Req Recom B/A After
PicForm - - 1 - 3
Work on file after upgrade NoUpg Req Recom B/A After
PicGIF - - - 1 -
PicMain - - - 3 -
Files with no issues detected NoUpg Req Recom B/A After
IPicInfo - - - - -
PicBMP - - - - -
Totals NoUpg Req Recom B/A After
Total number of issues - - 1 4 3
Issues/file 0,0 0,0 0,2 0,8 0,6
Issues/logical code line 0,00 0,00 0,00 0,01 0,01

Legend  
NoUpg Feature not upgradable
Req Fix required before upgrade
Recom Fix recommended before upgrade
B/A Can be fixed before or after upgrade
After Work required after upgrade

Detailed list of upgrade issues

Problem Count  
Feature not upgradable    
Fix required before upgrade    
Fix recommended before upgrade    
TTF/OTF fonts required by VB.NET 1  
Can be fixed before or after upgrade    
String byte functions unavailable in VB.NET 3  
Type unsupported by VB.NET 1  
Work required after upgrade    
Control unsupported by VB.NET 1  
Drag-and-drop requires rewrite for VB.NET 2  
Total 8  
Problems/logical code line 0,02  

Filter: <VB.NET Compatibility>

Problem descriptions

Control unsupported by VB.NET
A control type is not available in VB.NET. Image is auto-replaced by PictureBox. OLE Containers can be manually replaced by a browser control. MSComCtl2.UpDown won't upgrade but can be manually replaced by DomainUpDown or NumericUpDown controls. Work required after upgrade. VB.NET Compatibility. Severity: Info.
 
Drag-and-drop requires rewrite for VB.NET
VB.NET supports drag-and-drop functionality, but the object model is quite different. Drag-and-drop code must be rewritten. Work required after upgrade. VB.NET Compatibility. Severity: Info.
 
String byte functions unavailable in VB.NET
The byte versions of string handling functions are not available in VB.NET. Encoding and decoding functions in the System.Text namespace replace this functionality. The upgrade wizard does not automatically convert the byte functions. You may want to consider replacing them with the Unicode (wide) functions before upgrading. Affected functions: AscB, LenB, InStrB, ChrB, LeftB, MidB, RightB, InputB. Can be fixed before or after upgrade. VB.NET Compatibility. Severity: Warning.
 
TTF/OTF fonts required by VB.NET
If your application uses other fonts than TTF or OTF, these fonts will be changed to the system's default font, and all formatting (size, bold, italic, underline) will be lost. This applies to the default VB6 font MS Sans Serif. You might want to change all fonts before migration. Fix recommended before upgrade. VB.NET Compatibility. Severity: Warning.
 
Type unsupported by VB.NET
Fixed-length string and Currency are not available as data types in VB.NET. VB.NET will auto-convert Currency to Decimal, which has more precision. VB.NET has a replacement for fixed-length strings, but it is slow and limited. Arrays of fixed length string are not allowed at all. It is recommended to change all fixed-length strings to variable-length strings. Can be fixed before or after upgrade. VB.NET Compatibility. Severity: Warning.