G
Guest
Hi!
I have a system made of several DLLs, some in VB. Net, some in VB6. While
the VB6 part is not written in VB .Net we still use them and it's working
fine.
The problem is that we need to handle an operation that is fired in the .Net
part of the system and will end in a part that is in VB6 of the system and we
don't have enough time to re-write it...
To minize the impact of the adaptation and ease a "close" migration, I was
thinking about instantiate the VB6 DLL in .Net using Late Binding, but we use
OPTION STRICT set to ON and the rest you all know...
Is there a pre-processing directive that can turn off option strict just for
this method (and turn it on after it) or shoud I write an isolated class in
VB .Net with option strict Off with only one method used as a wrapper to the
VB6 DLL?
Thanks a lot,
I have a system made of several DLLs, some in VB. Net, some in VB6. While
the VB6 part is not written in VB .Net we still use them and it's working
fine.
The problem is that we need to handle an operation that is fired in the .Net
part of the system and will end in a part that is in VB6 of the system and we
don't have enough time to re-write it...
To minize the impact of the adaptation and ease a "close" migration, I was
thinking about instantiate the VB6 DLL in .Net using Late Binding, but we use
OPTION STRICT set to ON and the rest you all know...
Is there a pre-processing directive that can turn off option strict just for
this method (and turn it on after it) or shoud I write an isolated class in
VB .Net with option strict Off with only one method used as a wrapper to the
VB6 DLL?
Thanks a lot,