By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
457,885 Members | 1,191 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 457,885 IT Pros & Developers. It's quick & easy.

Problems with com dll

P: n/a
I have created a com dll with vb.net. I am having trouble getting it to
work on some of the development machines. It always works in the complied
project but on some of the development machines it cannot be created. The
dll project is a vb.net class library. The project it is being consumed in
is a vb6 exe and a vb6 activex dll group. I think the problem may have
something to do with threading but I don't know where to even start to look.
I have tried loading the .net project onto one of the problem machines and
compiling it. It still doen't work in the IDE but will work in the compiled
project.
Can anyone point me in a helpful direction ?

Thanks
Lauren
May 17 '07 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Can anyone point me in a helpful direction ?

1. is the class registred with regasm.exe on the target machine ( or with a
installer based system with the assembly marked as a com component )
2. does you com creatable class have a public sub new ??? as this is
required for a com component to start in legacy modus
3. my advice is to provide your own interface id`s

see this example i once wrote for this group

http://groups.google.com/group/micro...996d74d250974e

does this work ??

michel
"Lauren" <no@noneschreef in bericht
news:eE**************@TK2MSFTNGP02.phx.gbl...
>I have created a com dll with vb.net. I am having trouble getting it to
work on some of the development machines. It always works in the complied
project but on some of the development machines it cannot be created. The
dll project is a vb.net class library. The project it is being consumed in
is a vb6 exe and a vb6 activex dll group. I think the problem may have
something to do with threading but I don't know where to even start to
look. I have tried loading the .net project onto one of the problem
machines and compiling it. It still doen't work in the IDE but will work
in the compiled project.
Can anyone point me in a helpful direction ?

Thanks
Lauren

May 18 '07 #2

P: n/a
I have tried two methods of registering the class on the problem machine. I
first used the installer. Then I loaded the project and compiled the class
on that machine. The class works in a compiled exe, it only wont work in
the IDE.
The class does have a public sub New.
I created new ID's with the guid program for the class.

Thanks
"Michel Posseth [MCP]" <MS**@posseth.comwrote in message
news:eV**************@TK2MSFTNGP05.phx.gbl...
>Can anyone point me in a helpful direction ?

1. is the class registred with regasm.exe on the target machine ( or with
a installer based system with the assembly marked as a com component )
2. does you com creatable class have a public sub new ??? as this is
required for a com component to start in legacy modus
3. my advice is to provide your own interface id`s

see this example i once wrote for this group

http://groups.google.com/group/micro...996d74d250974e

does this work ??

michel
"Lauren" <no@noneschreef in bericht
news:eE**************@TK2MSFTNGP02.phx.gbl...
>>I have created a com dll with vb.net. I am having trouble getting it to
work on some of the development machines. It always works in the complied
project but on some of the development machines it cannot be created. The
dll project is a vb.net class library. The project it is being consumed
in is a vb6 exe and a vb6 activex dll group. I think the problem may have
something to do with threading but I don't know where to even start to
look. I have tried loading the .net project onto one of the problem
machines and compiling it. It still doen't work in the IDE but will work
in the compiled project.
Can anyone point me in a helpful direction ?

Thanks
Lauren


May 18 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.