Determine how the linked ball dbll vb6 is linked
I am a little excited because I was handed this ball for vb6 dll nodes.
The previous line of developer hardcoding in the DLL appears. The developer came out almost two years ago and I have no documentation and I have several different branches in the VSS database. Servers are moving, passwords have been changed.
My first goal is to try and run this utility. I believe I need to recompile all DLLs first for the new dll changes to take effect. I found one hiccup where the dll name seems to match a link in the Project References dialog, but the Project References dialog still says that this link is MISSING. Does anyone know how to solve this?
This code is also in an old VSS database that I would like to migrate to our TFS source control server. Is there an easy way to query the VSS server to find the latest developer changes so I can be sure I have the most recent version? It seems that the branches are not called logical.
It looks like I found that someone in the early stages is developing in n-tier development, however the architecture is hurting my brain. One layer looks in about twenty different ways to transform a recordset into a collection, an array, or simply return a recordset, and most of the "business logic" appears in stored procedures.
I think I understand why the developer in front of me and after the first one never tried to recompile this project ... I can't believe he was lucky enough to leave with it for almost two years, maybe that's why he left.
source to share
I found one hiccup where the dll name seems to match the link in in the Project Links dialog, but the Project Links dialog still says the link is MISSING.
I think I can at least answer this question. In all likelihood, the dll was not compiled with binary compatibility, or the original dll was not kept for compatibility. Without going into details, you will need to grab the (currently working) dll, install Binary Compatibility in the project, and point to the (currently working) dll for binary compatibility. Then your recompiled dll should show up correctly.
source to share