Use the project converter instead of the snippet converter: To do an accurate conversion, the project file contains important details, such as project level imports and references, which are critical to accurate conversions.
For example, without being able to unambiguously resolve all identifiers, it is difficult to fix casing errors (since VB is case insensitive) or determine if () should be converted to () or .
In addition, automatic C# compiler error fixing isn’t available in snippet conversions, since most won’t compile successfully even in VB without proper imports and references defined.
Prepare your VB.Net code: Make sure your VB.Net project compiles successfully, and all project references are valid.
Heed any VBConversions high-severity warnings issued before the conversion, and change the VB.Net code as suggested before reattempting the conversion.
Hold off on directly editing the C# code as long as possible: For any C# compiler errors encountered after the conversion, try to change the VB.Net code and reconvert rather than editing the C# code directly.
A unique feature of VBConversions is that it will fix most C# compiler errors automatically after the conversion by invoking the C# compiler and analyzing the error messages. However, this process can be cut short by an unexpected C# compiler error. You will have the best results if you can edit your VB.Net code to avoid the error and reconverting.