Citace od: Lael_Ophir kdy 01. 09. 2017, 18:32:26
Citace od: atarist kdy 01. 09. 2017, 17:33:08
Ale znam jednu firmu, co kdysi postavila svuj rozsahly SW mj. i na VB 6.0 (ano, technologie, ktera mela kdysi reklamy i na letistich atd.) a ted maji mega problem co dal.
Visual Studio obsahuje (obsahovalo?) wizard pro převod VB projektů na VB.NET. Nebylo to stoprocentní, nějaké změny bylo potřeba udělat ručně. Ale co jsem to kdysi před léty zkoušel na dvou projektech, tak těch ručních změn nebylo moc.
Samozrejme to nefungovalo, mozna tak na nejaky example s hello world, ale ne komplexni aplikace s ActiveX, COMem atd. Ostatne ta firma to resila primo s MS, bez vysledku (resp. jedine navrhovane reseni bylo udrzovat vbrun6.dll a nejaky hacky okolo toho). Mimochodem:
https://web-beta.archive.org/web/20141024003217/http://www.classicvb.org/petition/
Cituji z FAQ:
Can't VB6 code simply be recompiled in
VB.NET?
Sadly, no. The changes wrought to what Microsoft now calls Visual Basic really warranted a new name entirely, as the two languages are just that - two distinct languages. Microsoft provided a migration wizard intended to ease the transition from VB6 to
VB.NET, true. There is near-universal agreement that using this tool to port code assets is an incomplete solution at best, in that leaves myriad "TODO:"'s scattered throughout the translated code. At worst, the migration wizard is an extremely poor choice in that, unlike a complete rewrite, it doesn't take full advantage of all that the new platform offers.