Bizarre VB6 Make a mistake

Question

I have a really strange mistake, and any light that can be shed on him would be greatly appreciated. We are under the gun (as usual), and I need to quickly find the answer.

I made some changes to some source of VB6 that creates the COM object. The automatic build that creates our application returned an error. No problem, I thought I would just drop my changes. It’s good that my changes do not fix the problem.

In particular, when I try to create an application through a .vbg file, with a command line, for example, the path to vb6 \ vb6 ProjectFile.vbg / make

I get a message

"Compile error in file", line: Invalid object library or contains links to object definitions that cannot be found.

As I said, I returned the source code, so I am very fixated on why this error is still happening. Any VB6 gurus who can point me to the answer? I can publish the exact code, but the fact that it was built correctly has stopped building correctly and now refuses to build correctly, it makes me think that this is not a problem with my code, but rather some kind of problem in the environment. How something got into the registry as a result of a previous build error.

Any hints, tips or suggestions are greatly appreciated. I understand that my question is a bit sketchy, but I'm not even sure what is important to include and what is not.

EDIT:

Thanks for the great deals guys. I think this is due to the fact that VB6 does some kind of automatic registration.

: , vbp IDE. make .vbg, vbp. , , , .

2:

,

, , , . , , , . . SO; 10- , .

Answer 1

, VBG VBP . , CLSID, . IDE, , , .

Answer 2

, , COM COM. - , , , , VB6 GUID .

, , - , CLSID, .

cmsjr, CLSID .vbp .

, .tlb( ) olb ( ).

Answer 3

DLL . , VB6 . , Typelibs, IMPORT . , Binary DLL Ver 10 , Binary DLL Ver 9, . DLL , , TypeLib .

, DLL . , VB6 . DLL (, DLL Utility), . , .

, DLL- DLL-, DLL C. VB6, , C. , A , .

Answer 4

.obj .exp, .

Answer 5

You will need to open the project and re-enter the lines that you changed.
Save the project with VBG and recompile after that.

I think that will fix it.

EDIT: The idea is that the cls / bas file remembers the class (CLSID) that you used. So, if you change the links, but do not change the lines in cls / bas - this is a type mismatch (what was pointed out by vs, which is indicated in the cls / bas file).