(It contained code parts like a compatible FlexGrid and a very in. That is not the case with the so called Microsoft VB6Compatibility namespace, that has taken AFAIK 5 versions of VB.
#VISUAL BASIC POWER PACK FULL#
What your client asks is weird, the Microsoft Visual Basic namespace is a full continuing part of the. Net multiple applications.Ĭlient ask me that the result must be completely vb6 free, the question is abut Microsoft Visual Basic Power Packs, this controls are completely rewrited in ".Net" or use some interops vb6? My MSDN profile but will not answer coding question on either. Contact via my Twitter (Karen Payne) or Facebook (Karen Payne) via
Please remember to mark the replies as answers if they help and unmark them if they provide no help, this will help others who are looking for solutions to the same or similar problem. If you run into issues on the VB.NET side ask here while if there are issues that might cross between VB6 and.
So I would say start over if humanly possible. Then there are user interface controls, things like control arrays to contend with. rather than on error there are try/catch, rather than recordsets there is manage data providers, The best approach is to start out from scratch simply because (with no disrespect) how most vb6 developer's coded does not fit into the.
If not interested in a slow migration then I would not take this path but the toolkit is perfect if you have time to slowly bring the current project to. There is a library/toolkit, Microsoft InteropForms Toolkit 2.1 which is intended for a slow migration from VB6 to.
0 kommentar(er)
