VB.net conversion to C# issues?

  • Thread starter Thread starter Jay Balapa
  • Start date Start date
J

Jay Balapa

Hello,

I have been handed a VB.net windows compact framework project. Code contains
lot of legacy issues to deal with like modules. Previous programmer has used
modules all over the place. Scope of the project is to take the current XML
file database and port it to a SQL Ce one.

I really would like to convert it to c#. Is there a simpler way to get this
done. I dont want to spend a month doing this.

Thanks.
Jay.
 
what are you hoping to gain from the conversion to c#? sounds like
you're looking at some architecture changes that are out of scope for
the project - your better bang for the buck might be to focus on
centralizing the data access code which might take you a couple weeks
if it's a large app anyway. anyone that's going to use 'modules all
over the place' probably doesn't have a clean data access model. if
you start trying to rip out those modules, use singleton objects and
static variables for example, you're probably going to find yourself
wanting to re-architect the entire thing and find yourself with a big
mess on your hands and nothing working. start with the data access and
dig back into the conversion as a separate project - that's my advice
from your initial description.

that said, there are code converters - www.csharpenerforvb.com,
www.vbconversions.com - those are ads that pop up with your question.
it's a slippery slope...
 
Hi,

Thanks for the quick response.

Iam just going to do as you stated. Just strip out the data access code from
the modules and use static classes for conversion to SQL CE.

Not worry about existing code.

-jay.
 
Back
Top