Our C# developer has found it very useful for helping him work through an old VB.Net application.  Reviewing the converted code, allows him to get a better understanding of the VB code, so he can make tweaks in VB, without having to do a complete rewrite.

Brent

Congratulations!

Converter 5.05 is an excellent tool. I have my VB application converted to:

C# comment lines: 32,475
C# empty lines: 4,316
C# pure code lines: 94,872
—————————————————
Total C# lines: 131,663
Non-C# lines: 9,350
=============================
All lines: 141,013

Without problems and had to edit only a few lines by hand.

Really a big time saver!

With best thanks

Peter

Wow, what a product VBConversion’s VB to C# is!!!

21,000 lines of VB is converted and working.
The resultant C# GUI looks exactly like the VB GUI, and it’s passing my built-in regression test, which was also automatically converted.

This is very important for my client. I used VB to initially create the prototype GUI because VB has lots of features that substantially speed up development.
But now that we have this baseline software, we wanted it in C# for obvious reasons (more available programmers, available libraries, and stackoverflow support).

Thanks for an outstanding product!

I was really convinced to use it by the online blog of the VBConversions comparison with (competitor name ommitted), which was a disaster and not even in the same league as VBConversions.

I am sure the conversion software is very complicated. It works far better than I thought it would, meaning I didn’t think I could find a software solution that would convert the code as far as yours did. I had 110,000 lines of code and it saved me at least 8 weeks of work doing a manual conversion.

I was skeptical. I’d used other conversion software, and it never compiled without requiring tons of manual fixes. In the end it was easier to either give up or re-write it from scratch. I didn’t really think it was possible to convert one to the other automatically.

However, on my FIRST try with VBConversions, converting a 5000 line piece of vb.net software, it converted the entire project, and WITHOUT ONE SINGLE MANUAL EDIT, the program compiled and ran in C#. Now you can call me a believer. It’s simply astounding what has been accomplished in this software. He has done what I thought was impossible. It’s the only conversion software worth getting.

I would like to commend your company on your excellent service. Your turnaround time for responses are so appreciated. We have and will recommend your product and company to any shop dealing with converting VB.net to C#.

I’ve used your VB.Net to C# Converter product since 2005 and find it to be one of the best software investments I have ever made.

Your application worked great the very first time unlike my experience with (competitor name omitted) which does not do spit with the designer file and made a mess out of the conversion of the remainder of a functioning vb.net application.

I’ll be recommending your application to anyone else I run into that may be attempting to move from vb.net to C#. You’ve earned my confidence!

I just downloaded your trial software for VBConversions (to C#) and all I can say is wow! Great software! Keep up the great work. Being in the industry as long as I have I have seen a lot of bad software both in the corporations as well as with vendors. It has always been a pleasant surprise to find something that simply works as well as advertised.

We had nearly 50 MB’s of VB.Net code to convert. The code effected many development teams in different departments within the enterprise.

Converting all of this code to C# was a daunting task, one that we could not consider doing manually. We found out that almost no tool can do this job without a hitch. Some tools that appeared to work well, made their own “Decisions” about the original intent of the code. Sometimes right, sometimes not so right.

We needed a product that didn’t just convert the code, but also gave us statistics, reports and drill down analysis.

We intensively tested 6 products, and VBConversions’ VB.Net to C# Converter had the richest feature set, reporting tools, analysis and recording options. It converted the code at or above the 99.5 % rate, and gave excellent feedback suggestions and reports how where errors did occur, and what to do to fix them.

In short, all things considered, this is absolutely the best tool for the job.

It made the job of converting this code a relatively minor task in the project timeline, letting us move on to the job of extending this code into the SOA – Web Services Architecture we are moving it to.

We knew better than to think that we could push a button and get our 50,000 lines of UI code, 700 business objects, and 9000 lines of data access code converted flawlessly. No tool does that.

What we needed was a tool that could convert 99% of the code and then give us detailed reports on the other 1% that might require examination on our part. This C# converter is that tool. This 1% of code that did not convert cleanly turned out to be poor code that we needed to cleanup anyway, or it was code that had little to no equivalent in C#.

Furthermore, support of the product has been outstanding. Because of the nature of our system and an odd pattern much of our UI code followed, we truly needed the converter to behave slightly different.

After a few conversations via email, a new version of the code was released and it specifically made our issue a non-issue.

Try getting that out of any development firm!

I have no problem recommending this product.

Hi,

We bought your product today and in just one project it has saved several hours of conversion work.

I recently needed to convert about 6000 lines of code. I purchased this converter and I can say that it is a great tool.

Even though I used this tool only once, it was well spent money. Keep up the good work.

Wow, what a product VBConversion’s VB to C# is!!!

21,000 lines of VB is converted and working.
The resultant C# GUI looks exactly like the VB GUI, and it’s passing my built-in regression test, which was also automatically converted.

This is very important for my client. I used VB to initially create the prototype GUI because VB has lots of features that substantially speed up development.
But now that we have this baseline software, we wanted it in C# for obvious reasons (more available programmers, available libraries, and stackoverflow support).

Thanks for an outstanding product!

I was really convinced to use it by the online blog of the VBConversions comparison with (competitor name omitted) , which was a disaster and not even in the same league as VBConversions.