Problem with VB DLL

[Prashant]

Hi,
We are doing a VB project (named WinApp), for that we also created a "VB ActiveX DLL" project (named ProjectDLL) and making reference from "WinApp” to "ProjectDLL". Now the problem is if we install both projects and later if we upgrade "ProjectDLL" and reinstall it on client system then we am getting following error:

Run-time error '430':
Class does not support Automation or does not support expected interface


But if we recompile the "WinApp" project after compiling "ProjectDLL" then it works fine.
Is there any solution for this problem? (Actually we don't want to recompile WinApp project every time) I guess this problem is due to version comparability. Is it possible to use "VB ActiveX DLL" without making reference in other VB projects? We was trying 'Private Declare Function MyFun Lib "ProjectDLL"..' but it is helpless. Please help us regarding that, Thanks in advance.

Prashant

[Joacim Andersson]

For your AX DLL project click Project > Properties in the VB IDE, select the Component tab and set the Version Compatibility to "Binary Compatibility" and browse to where you have the latest compiled DLL.

This will ensure that when you recompile the DLL that it stays compatible with the old version, as long as you haven't changed the code so the compatibility is broken but VB will then scream that out very loud to you

Cheers,

[khalik_ash]

well Prashant why are u deploying as 2 sperate projects.. when u are reference ProjectDLL in WinApp u need to ship ur WinApp.. with chnages in ProjectDLL if u dont want the entire package then get patches.. with only the changes..... what packing and deployment tool are u using,... currenlty i am using wise windows installer and that work fine with patches.... and iwll help u