In your position, I'd suggest sitting down with a notebook and spending a few days drawing a kind of roadmap of how the program works. So get your ego ready for a lot of, "I thought I was done, but missed this feature."
#Vbuc com code#
Old code almost never has this, though, and odds are there isn't sufficient documentation for you to understand all of the needs. If the old code has a suite of automated tests, that's a luxury: you can port the tests to prove your port satisfies the old requirements. The biggest issue with porting old code, whether you rewrite or try to convert, is proving you haven't introduced an error. That the conversion tool failed doesn't say a lot, it only really works for the trivial parts of code. You have to understand a good deal about both languages involved in the port, and VB6 has quite a few quirks that cause some friction when porting to C#. However, porting an app's tough at the internship level. I'm used to working with 50k+ lines so 6k feels relatively small and cozy to me. To me, 6k lines is within the realm where it's realistic to consider either choice. Do I create a new project and start from scratch, or try to fix the converted code? Resulted in a few errors and obsolete methods.
#Vbuc com upgrade#
TL DR- Used VBUC to upgrade old visual basic code. Looking at it from the other side though, fixing the converted code might lead to more problems down the line, with a sort of domino effect (replace one obsolete method, end up with 50 errors from replacing it). Considering that the old VB Project has 6000+ lines of code, I figure it'll take more than a while to remake and I could end up saving time trying to fix the converted code. However, the result of the conversion ended up with a few errors, obsolete calls/methods and a handful of other problems.Īt this point, I have no clue whether to try and go about fixing the converted code, or starting a new project. To make my life easier, I tried using VBUC, (Visual basic upgrade companion) to try and save me some pain in updating the code. Working on a project for my summer internship involving upgrading and updating some programs from good old VB6 to c#. Read detailed descriptions of the rules here. Rule 7- Submitted links to be made with effort and quality.Rule 6- No spam of tools/companies/advertisements for financial gain.Rule 5- No hostility towards users for any reason.
Rule 3- Posts should be directly relevant to C#.
#Vbuc com software#
0 kommentar(er)
