EWIs

The following section provides useful information about the messages (comments) that will appear on your upgraded code and how to solve them.

Working with EWIs

The number of EWIs in your code depends entirely on your programming style and the size, type and complexity of files that you want to upgrade. As a general rule, forms usually have more issues than classes and modules, because forms have a richer object model and significant transformations must be applied when upgrading to Windows Forms.

Steps to fix a migration issue

This section shows the recommended steps to fix an error related to EWIs. The steps are:

1. Locate the source of the problem

2. Understand the code purpose in the original VB6 application

3. Identify a solution in .NET

4. Implement the solution

5. Mobilize.NET Customization

6. Document the solution

Locate the source of the problem

To find the source of the problem, you can add some breakpoints a few lines before the code where the exception or the different behavior manifests itself. You need to do this in both the original VB6 code and the upgraded code so that you can compare to find out what is causing the problem or why the problem is occurring.

Understand the code purpose in the original VB6 application

The next step is to understand, in the original VB6 application, the functionality of the section of the code causing the problem. You can perform the following activities to understand the original behavior:

1. Create small examples of code that use the same features.

2. Execute step by step (debug mode), as many times as you need, the section of code causing the problem.

Identify a solution in .NET

Once the functionality of the original VB6 application is understood, the next step is to replicate the same functionality in the upgraded .NET application. Some recommendations for this are:

1. Create small examples in .NET to replicate the VB6 functionality.

2. Review the related .NET documentation on the web to determine how to achieve the same functionality in .NET.

3. Ask your peers or a Mobilize.NET migration expert.

Implement the solution

If you already have a solution, you can implement it. Once you have modified the upgraded code and the found solution was implemented, you need to test your code to confirm that the behavior is the same as the original VB6 application. You can, also, review the rest of the upgraded code to determine if the same problem is present in other areas.

Mobilize.NET Customization (optional)

In some cases, you can consider Mobilize.NET Customization. Several factors must be taken into account at this point:

1. Timing

   • Will the current timeframe of the project allows the Mobilize Team to implement the required customization? Is the impact of the error large enough to justify it to be reported in order to be included in future releases used in future projects?

2. Complexity

   • Is there an opportunity to make the replacement in several places using another automated solution such as Regular Expressions?

3. Rework required

   • Are the manual changes performed at this point in the project so many that executing a code merge will imply too much additional work?

Document the solution

Once the solution is implemented and the problem is resolved, it is important that the solution is properly documented and stored in a shared knowledge base. This helps in cases where other developers run into the same issue and are able to access information on how to solve it.

EWIs Lists

In the following lists, you can see the most common EWIs. It is important to know that there are many other EWIs not described in those lists.

Warnings

Below are a few of the most common warnings generated by the Visual Basic Upgrade Companion.

Code number	Description
206	Untranslated statement in %1. Please check source code
1003	ParamArray %1 was changed from ByRef to ByVal
1044	Sub Main in a DLL won't get called
1047	Application will terminate when Sub Main() finishes
1049	Use of Null/IsNull() detected
1063	Arrays in structure %1 may need to be initialized before they can be used
1068	%1 of type %2 is being forced to %3
2050	%1 Event %2.%3 was not upgraded
2065	%1 %2 %3.%4 has a new behavior
2074	%1 %2 %3.%4 was upgraded to %5.%6 which has a new behavior
2077	Change the default 0 index in the Rows property with the correct one
2080	%1 was upgraded to %2 and has a new behavior
2081	%1 has a new behavior
2099	Return value for Dir has a new behavior
6002	UserControl Event %1 is not supported
6021	Casting 'int' to Enum may cause different behavior
6022	The CommonDialog CancelError property is not supported in .NET
7005	Parameters (if any) must be set using the Arguments property of ProcessStartInfo
7006	The named argument %1 was not resolved and corresponds to the following expression %2
7008	The ProgId could not be found on computer where this application was migrated
7009	Multiples invocations to ShowDialog in Forms with ActiveX Controls might throw runtime exceptions
8007	Trying to marshal a non Blittable Type (%1). A special conversion might be required at this point. Moreover use 'External Marshalling attributes for Structs' feature enabled if required

Issues

Below are a few of the most common issues generated by the Visual Basic Upgrade Companion.

Code number	Description
1002	Lset cannot assign one type to another
1010	The preceding line couldn't be parsed
1014	%1 statement is not supported
1043	Class instancing was changed to public
1046	%1 Parameter '%2' is not supported and was removed
2038	Form property %1.ScaleMode is not supported
2064	%1 %2 %3 %4 was not upgraded
2068	%1 %2 was not upgraded
2070	Constant %1 was not upgraded
7003	The Hdc should be released once it is used for safety

ToDos

Below are a few of the most common ToDos generated by the Visual Basic Upgrade Companion.

Code number	Description
1035	#If #EndIf block was not upgraded because the expression %1 did not evaluate to True or was not evaluated
1050	Structure %1 may require marshalling attributes to be passed as an argument in this Declare statement
1059	Code was upgraded to use %1 which may not have the same behavior
1065	Error handling statement (%1) could not be converted
1067	Member %2 is not defined in type %3
1069	Error handling statement (%1) was converted to a pattern that might have a different behavior
2018	Remove the next line of code to stop form from automatically showing
2045	Only TrueType and OpenType fonts are supported in Windows Forms
7010	The connection string must be verified to fullfill the .NET data provider connection string requirements
7016	This property was auto-generated because it is used in WriteProperties but does not exist.
	How to prevent the application from exiting immediately after starting

Notes

Below are a few of the most common Notes generated by the Visual Basic Upgrade Companion.

Code number	Description
2041	The following line was commented
6016	Structure %1 should be within the shared file due to its use in Declare statement for a Windows API
7001	The following %1 (%2) seems to be dead code
8001	Element %1 was removed
8008	Element %1 is obsolete and should be removed