Jump to content

Missing .dll Upon Conversion


abowlin

Recommended Posts

Converting a vb6 program into a vb.net program appeared to be successful, but upon attempting to build the program in visual studio 2017, I am getting the error below. It appears that a .dll has not been created by the conversion software. How can I create this .dll or how can I configure the conversion tool to create the .dll successfully?


Error    BC2017    could not find library 'C:\Users\abowlin\Documents\Anthony M. Bowlin (2018)\Jobs\TRW Msetup Conversion 2\TRW Lebanon Version_.Net\Upgraded\AMB_Test5Support\bin\Debug\AMB_Test5Support.dll'

Link to comment
Share on other sites

  • Mobilize.Net Staff

Visual Studio is telling you that you have a dependency on a DLL (AMB_Test5Support.dll) that it can't find in the location listed in your project file. Check your development environment and point VS to the correct path for that DLL and you should be ok.

Link to comment
Share on other sites

That makes sense, but my concern is that AMB_Test5Support.dll does not exist. It is not in the upgrade folder created by the VBUC and was not a previously existing .dll on my computer. Is it possible the VBUC should have created the .dll but in fact did not?

Link to comment
Share on other sites

  • Mobilize.Net Staff
1 hour ago, abowlin said:

That makes sense, but my concern is that AMB_Test5Support.dll does not exist. It is not in the upgrade folder created by the VBUC and was not a previously existing .dll on my computer. Is it possible the VBUC should have created the .dll but in fact did not?

Look in the VBUC references screen to see if that DLL was referenced by your original VB6 project. The VBUC would not create this--it's some kind of private library, not a Microsoft .NET library. 

vbuc_refs.JPG

Link to comment
Share on other sites

  • 1 year later...
  • Mobilize.Net Staff

During the conversion, the VBUC will generate a Support project as part of the migration.

This Support project will contain the stub methods generated by the tool as well as all the API calls which are extracted by the tool and centralized in a single project.

The manual process of the migration should start by compiling the helper classes (if you included them as source) and then compiling the Support project. After this you can begin compiling the migrated projects (which will likely have a reference to the support project).

 

I hope this helps.

 

- Will

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Terms of Use