debug after vb6 migration  
Author Message
preed_lahey





PostPosted: Visual Basic General, debug after vb6 migration Top

Any advice on issues with debugging a migrated vb6 dll Setup appears correct with an external program defined and starting when debug is started. Breakpoints are set, but never reached.

It appears that the application is still referencing the installed (production) version of the dll (still vb6), rather than the debug version (.net). Perhaps registry settings are not being adjusted to support use of the debug version

Any suggestions would be appreciated.



Visual Basic17  
 
 
nobugz





PostPosted: Visual Basic General, debug after vb6 migration Top

To remove any doubt, unregister the original component with regsvr32 /u. Make sure you've registered the debug version of the .NET module with regasm.