ACTIVEX DLL

[scasystems]

Have various ActiveX DLL's that are shared across applications. The reason for developing the DLL's
was so that if any erors were found then instead of packaging and redeploying the application, we could just transmit the DLL which had been corrected.
Yet although a minor change within a function (not adding or changing the number of parameters etc) was done. when
the dll is copied over the original I still get automation
error when starting the application.
I haven't got automatic version ticked as this is done manually.
I have re-registered the dll but still get the error. The only way I can get it to work is re-install the application????
Another thing I have noticed is that if any dll or the exe is changed but the version number is not incremented the install will not overwrite the existing versions.

Cheers in advance. Only just joined the forum but the help is appreciated. Just wish they would get the search on keywords sorted.

 

[scasystems]

Ahh! Sorted it. Have changed a private variable.
Also still have to send the application.exe with the DLL

While I am here. I actually use project compatability for the DLL's. I haven't found much in the way of documentation on using binary compatibility etc any help on usefull links

cheers

 

[LazyMe]

Once your dll is in use by clients, you should switch to binary compatibility. This way, when compiling your dll, you'll be warned when the bin comp has been broken. You can then choose to restore the bin comp by resolving the problems otherwise (usually not possible) or recompile the client as well against the new public interface of the dll.

I'm not sure how the pdw handles installs (haven't used it for a long time). Usually you can specify how to overwrite exisiting files (or rather WHEN to overwrite existing files). For instance by checking against the version number, the datestamp etc. It might be so that your installer only checks the version number and, if the same, does not check for the date to overwrite it.
Greetings,
Rick