Upgrade: Use prepared Interop assemblies

  • Thread starter Thread starter Armin Zingler
  • Start date Start date
A

Armin Zingler

Hi group,

after waiting more than 4 month in the .upgrade group for an answer, I dare
to ask here. :-)

I open a VB6 project in VB 2008 (express) and have the Wizard convert it. It
also creates the necessary interop assemblies for the referenced ActiveX
dlls.

Problem: the interop assemblies are not imported the way they should. The
result looks as if the "/sysarray" argument has been used for tlbimp.exe. As
this does not fit my needs, I created the interop assemblies manually in
advance. Now, if I wanted to have the wizard upgrade the project, how could
I tell it to use the prepared interop assemblies?

It is /not/ an option to replace the automatically created interop
assemblies by mine /after/ the wizard has done it's job. The reason is that
the result of the upgrade job depends on the interop assemblies. So,
afterwards it is too late.

Thanks in advance


Armin
 
Armin Zingler said:
Hi group,

after waiting more than 4 month in the .upgrade group for an answer,
I dare to ask here. :-)

I open a VB6 project in VB 2008 (express) and have the Wizard
convert it. It also creates the necessary interop assemblies for the
referenced ActiveX dlls.

Problem: the interop assemblies are not imported the way they
should. The result looks as if the "/sysarray" argument has been
used for tlbimp.exe. As this does not fit my needs, I created the
interop assemblies manually in advance. Now, if I wanted to have the
wizard upgrade the project, how could I tell it to use the prepared
interop assemblies?

It is /not/ an option to replace the automatically created interop
assemblies by mine /after/ the wizard has done it's job. The reason
is that the result of the upgrade job depends on the interop
assemblies. So, afterwards it is too late.

Thanks in advance
Click to expand...

Any clue?

Thx!


Armin
 
Back
Top