Test Results

Since its first release in 2004 and initial testing on the 101 Visual Basic.Net and C# Code Samples from Microsoft, VBConversions has adopted a “test-first” approach. VB.Net has no rigorous formal definition and new surprises await at every turn, made more complex by new releases of Visual Studio and the .Net Framework. This necessitates a pragmatic massive testing strategy, and VBConversions has amassed a test bed of over 15,000 projects to that end, and the numbers grow with every release.

By The Numbers

15,348 projects converted
12,609,059 VB.Net lines of code converted
15,110,422 C# lines of code produced

Test Methodology

Once on the list, a project is never taken off
New projects added with each release
All VB versions are tested
All project types are tested
The native multi-project conversion feature of the converter is used

Where Do The Projects Come From?

With each release, new programs are added to the test suite via public and private sources, and created in-house to test a variety of conditions. Also, with each new release of Visual Studio, existing projects are upgraded to test new, often undocumented C# compiler error messages and message format changes.

New projects come from:

Downloads from on-line open-source sites
Sample projects from popular third-party tools
Private submissions
In-house project creation
Upgrades from previous versions

How Are These Conversions So Accurate?

VBConversions’ superior accuracy is no accident. Its architecture used wasn’t chosen for its ease of initial building, but for maximum accuracy at any cost. Code is hand written in .Net languages and your VB.Net code is first understood, then translated. The final use of the Microsoft C# compiler to validate accuracy and fix remaining errors in the conversion is unique to VBConversions and demonstratively responsible for a significant accuracy advantage over other converters.