Registry 1

[UncleCake]

Hi,

Each time I edit a dll I compile it, it shows up as a new instance when I go to Tools >> References. On some of them it displays 5 or 6 times in the References. If I do a regsvr32 /u C:\...... first does that uninstall the dll and get rid of the reference? I am kinda lost, can someone help?

-Uncle Cake

 

[CasperTFG]

Hey Uncle I have the same issues over and over, when re conpilling DLL's I find the problem only occurs with me, If I re-compile the DLL's when they are part of a VBG.

I suggest hiding or moving off all the DLL's you want to clean, then run a registry cleaner, then replace the DLL's and recompile... Craig, mailto:sander@cogeco.ca

Remember not to name the Lambs...
It only makes the chops harder to swallow

 

[muesli]

Try setting Project Compatibilty in the project properties dialog. This should stop VB from writing new typelib ID's to the registry each time you compile.

 

[UncleCake]

Can you tell me what setting the Version Compatibility to Project Compatibility does? I looked it up and it doesn't really say what it does.

-Uncle Cake

 

[CasperTFG]

Okay here is my best attempt at explaining it. You develop a program with amny DLLs. You open the project in a group, i.e. You have the EXE and all DLL's open in 1 Project window.

If you set version Compatibility, then your program will use the DLL that is compiled. If you set it to Project, it will ignore the compiled DLL, and use the active code.

Binary compatibility is used for MTX and COM. Craig, mailto:sander@cogeco.ca

Remember not to name the Lambs...
It only makes the chops harder to swallow

 

[UncleCake]

Ok, thanks for the info!

-Uncle Cake

 

[CajunCenturion]

good info Craig - a star for you Good Luck
------------
Select * from Users where Clue > 0
0 rows returned