vb.net upgrade:
Hi- (x-posted in dotnet.framework.adonet)
i have been struggling with porting a large VB6 project over 55 forms, 5
data environment objects, each with 50-100 commands (over 30 total), plus all
the hand-coded connections, commands and recordsets where applicable.
And with the Crystal Reports XI RDC, now a total bitch to deal with. Running
the code mangler (converter) just timed out until I removed all references to
Crystal Reports. I am still faced with an ungodly amount of flagged ADO
code, along with many instances of missing objects where there was now
applicable replacements Hierarchial flex-grid, datagrid, datalist, datacombo).
So I guess this point I am asking myself, should I try to get this thing
running, not to mention having to use the compatibility libraries and code
band-aids to run with the ADO stuff? I have over 1500 issues to fix
(including 590 outright errors) before I can even build this thing. Perhaps I
should do a re-write.
I think the bulk of the work is going to be converting all that data
environment stuff into .NET code. Then hand-writing all the code to bind it
to what's left of the existing controls.
I did see that there is a dataform wizard, but when I looked into it, it
appears to only generate oledb provider object code instead of code for the
SQL Server provider that I keep reading I NEED to be using. Even changing
that generated code over to the SQL provider is a major PIA. AND, I cannot
believe all of the freakin' code that wizard puked out for one lousy select
statement on 10 columns of data. I will be hand-coding until next summer if
this is required of each ported command.
Anyone with similar experience? Was is worth it? Is there a tried-and-true
process to go from a boat-load of data environment objects bound to Activex
controls, either directly, or through hand-written code? Any advice, help,
flame appreciated.
--
thx,
jf kaminsky
--
thx,
