visual sourcesafe - Determine how a knot ball of vb6 dlls are tied together -


I'm getting bored a bit because I have been handed over to this knot of VB 6 DLS.

This previous developer appears hard-coded connection strings in DLS. The developer left about two years ago and I do not have any documents and I have several different branches in a VSS database, there is a step in the server, the passwords have been changed.

My first goal is to raise and run this contraption. I believe that I have to first compile all the DLLs in DLL so that the new DLL changes can take effect. I have received a hiccup where the name of the DLL matches in the "Project Reference" dialog, but the project reference dialog still says that the reference is erasing. Does anyone know how to solve this?

This code is also in an old VSS database which I would like to transfer to our TFS source control server. The VSS server is an easy way to query the latest changes made by the developer, so that I can trust that my most recent version is? Branches are not considered to be rational.

It appears that I have discovered some kind of initial effort, though the architecture is painful to my brain. A layer experiences approximately 20 different ways to make a collection in the form of a record, changing the array or simply returning the record set, and most of the "business logic" appears in stored procedures.

I think that why the developer first and I have never tried to compile the project first ... I can not believe that he has been waiting for a lot to participate with it for almost two years. He was lucky, perhaps because he left

So I need DLS regsvr32 ... o. I just learned that DLL is hell .


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -