Rdeference to activex dll disappears when I rebuild the acti

Hal Tz · Joined: 04 Oct 2007 Posts: 1

Hi, I hope this is the right place for this. Using VB 6.0 , I am building an
activex DLL. It exports a class with some functions, which I call from a
standard exe. The exe has the activex dll as a reference
(Project..References). Whenever I rebuild the DLL (and even if I run regsvr32
on it after a build), when I then load the exe project, I get the error
"Could not create reference" followed by the full pathname to the dll. I then
look at the Project references for the exe and the reference to my dll is
gone. I add the reference again and all's well until the next time I rebuild
the dll. What am I missing?
--
Hal

Archived from group: microsoft>public>vb>ole

Brian Muth · Joined: 04 Oct 2007 Posts: 18

In your DLL project, select properties. Under the Component tab, select
Binary Compatibility.

Otherwise, VB6 automatically generates new GUID's for your coclass and
interface, but your Project..References is still pointing to the old GUID's.

Brian

"Hal Tz" wrote in message@microsoft.com...
> Hi, I hope this is the right place for this. Using VB 6.0 , I am building
an
> activex DLL. It exports a class with some functions, which I call from a
> standard exe. The exe has the activex dll as a reference
> (Project..References). Whenever I rebuild the DLL (and even if I run
regsvr32
> on it after a build), when I then load the exe project, I get the error
> "Could not create reference" followed by the full pathname to the dll. I
then
> look at the Project references for the exe and the reference to my dll is
> gone. I add the reference again and all's well until the next time I
rebuild
> the dll. What am I missing?
> --
> Hal

Rajneesh Noonia · Joined: 04 Oct 2007 Posts: 12

Under Project Properties > Components > Verion Compatibily options
This option is used to set the backward compatibility with previous version
of your components.If you chose no compatibility.. vb6 create new GUIDs for
you components and other clients which are refreing to you component breaks.
Create folder vercom and copy the old verion of your DLL.Open the dll prject
and set the binary compatibility option ..Now whenevr you update the dll
project and recompile vb will maintan the old GUID's and hence your component
will not break..

Regards
Rajneesh

"Hal Tz" wrote:

> Hi, I hope this is the right place for this. Using VB 6.0 , I am building an
> activex DLL. It exports a class with some functions, which I call from a
> standard exe. The exe has the activex dll as a reference
> (Project..References). Whenever I rebuild the DLL (and even if I run regsvr32
> on it after a build), when I then load the exe project, I get the error
> "Could not create reference" followed by the full pathname to the dll. I then
> look at the Project references for the exe and the reference to my dll is
> gone. I add the reference again and all's well until the next time I rebuild
> the dll. What am I missing?
> --
> Hal