Comments on: VB.Net vs C# in Visual Studio 2005 http://www.wackylabs.net/2006/11/vbnet-vs-c-in-visual-studio-2005/ Mostly code, sometimes something else, always slightly wacky. Mon, 06 Feb 2012 08:55:22 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Mark http://www.wackylabs.net/2006/11/vbnet-vs-c-in-visual-studio-2005/#comment-366 Mark Mon, 20 Nov 2006 04:35:48 +0000 http://www.wackylabs.net/2006/11/vbnet-vs-c-in-visual-studio-2005/#comment-366 Thanks for sharing your experience. At my prior employer, we faced a huge VB upgrade (over 500 VBPs) we had already standardized on C# for new code and we had alot of it. We did not want to deal with learning and supporting VB.NET too. We were determined to go to C#, and we knew we should leverage our VB6 code as much as possible. Afterall, the VB6 codebase described in detail the layouts and logic for hundreds of forms/controls, it had detailed specs for thousands of DB/service calls, and it had thousands of business logic algorithms. The VB upgrade wizard tool was no help, so we hired a translation tool vendor to build us a custom VB to C# translator. See the October 2006 .NET developer journal article "Five Pillars of VB Retirement" for the case study. Thanks for sharing your experience. At my prior employer, we faced a huge VB upgrade (over 500 VBPs) we had already standardized on C# for new code and we had alot of it. We did not want to deal with learning and supporting VB.NET too.

We were determined to go to C#, and we knew we should leverage our VB6 code as much as possible. Afterall, the VB6 codebase described in detail the layouts and logic for hundreds of forms/controls, it had detailed specs for thousands of DB/service calls, and it had thousands of business logic algorithms. The VB upgrade wizard tool was no help, so we hired a translation tool vendor to build us a custom VB to C# translator.

See the October 2006 .NET developer journal article “Five Pillars of VB Retirement” for the case study.

]]>