I have a .NET assembly that has 2 classes. One of them has 2 events exposed
and the second one has 1 event exposed to the user. Both these classes have
been exposed to COM.
Now, when I use the assembly in VB6, I use the withevents keyword to
subscribe to the first event in the first class. However, for some reason, I
need to add code for the second event and also the event in the second class
for the VB6 program to work. Why is the VB6 compiler forcing me to subscribe
(and add code) to all the events when I just want to subscribe to one? Is
there a compiler switch or something I can change in the assembly that will
prevent this?
Thanks,
MT
Christian Fröschlin - 08 Sep 2003 16:26 GMT
> subscribe to the first event in the first class. However, for some reason, I
> need to add code for the second event and also the event in the second class
> for the VB6 program to work. Why is the VB6 compiler forcing me to subscribe
> (and add code) to all the events when I just want to subscribe to one?
I never heard of a problem like this. Please provide some
more details. As a side note, there seems to be a problem
(crash?) when holding multiple WithEvents references to a
single Interop object in VB6.