Visual Basic

VB 2005 - sharing a COM dll problem

21-Mar-07 9:10

opmfa1850 wrote:
i want the code in vb6 plz

Since you put it that way....here[^].

Dave Kreskowiak
Microsoft MVP - Visual Basic

Re: serial port

chamal77721-Mar-07 20:33

chamal777

21-Mar-07 20:33

how to code for serial port

LittleEd21-Mar-07 8:52

21-Mar-07 8:52

Hi - hope this the right place for VB 2005 problem...

I've written a COM dll in VB 2005. I'm using the objects without problem on the machine I compile on. Using them in excel, everything great.

However, when I try to use the dll on another machine no joy at all. I have registered OK (copied from the registry on the compliation machine), the GUID's etc check out fine.

When I reference the dll (actually the .tbl file) in XL it seems to be OK. I can see the objects in the XL VB IDE, they look cool. I can step through code but when I get to an instantiation (like Set X = new MyObj) VB throws an error "ActiveX component can't be created"
??

I've checked registry, installed VB 2005 on the non-compilation machine. No joy.

After a couple of days on this need some help? Any ideas?? Could this be as assembly problem?

Distributing a dll in c++ was never this painful (once it ciomplied ... Smile | :)

)!

cheers for the input

gazza

Dave Kreskowiak21-Mar-07 9:10

21-Mar-07 9:10

Did you register the assembly using RegAsm or did you just try to copy the keys yourself?

Dave Kreskowiak
Microsoft MVP - Visual Basic

LittleEd21-Mar-07 12:58

21-Mar-07 12:58

thks

I tried using RegAsm with 2 variants on the command line

RegAsm mydll.dll

and with the /tbl option

RegAsm mydll.dll /tbl:Mydll.tbl

I haven't got the error messages to hand but didn't work.

On the key question, I exported them to a .reg file on the compiling machine and re-imported on the new machine. The key *looks* to be OK.

there is a chapter on assemblies in Balena that I have started to go through but nothing useful yet.

thks for your reply.

Dave Kreskowiak22-Mar-07 5:20

22-Mar-07 5:20

Well, the other problem could be that your library code isn't decorated with COM attributes properly or completely.

You really DON'T want to just export the registry key and import it on another machine, there's definitly more than one key that has to be created!

Also, when you use RegAsm, if you don't use the CodeBase switch, you MUST either put your .DLL in the same folder as the .EXE client app that's using your COM objects, or you must install it into the GAC, but your assembly has to have a strong name to do that. If you don't, you can get the error that you're talking about.

If you use the CodeBase switch, you can register the .DLL where you want to put it, so long as it doesn't move after the registration is done.

C:\My Folder> REGASM MyComAssembly.dll /tbl:MyComAssembly.tlb /CodeBase

When I'm creating an assembly I want to expose to COM, this[^] is the step-by-step sheet I follow.

Dave Kreskowiak
Microsoft MVP - Visual Basic

LittleEd23-Mar-07 4:08

23-Mar-07 4:08

thks

I am running .NET 2.0.50727

1. was using RegAsm ver 1.?? previously. Now using ver 2.0.50727.42 and I can register - I have done this now as indicated with the /tbl & /codebase as indicated on 2 machines with success.

Recall I am trying to use the objects in excel(.exe) through the VBA interface.

I find:

1. If I regsiter in an arbitrary directory on a client machine some interesting effects. When i try and instantiate I get "run-time error '-2147024894 (8007002)' File or assembly name "MyClass", or one of its dependencies, was not found"

2. If I regsiter in the excel.exe directory on a client machine, i try and instantiate I get
"run-time error '-2146234105 (80131107)' The format of the file "MyClass" is invalid.

had a sniff around, these errors have been seen before but I haven't found a solution to them.

In an attempt to "back-engineer" I have built some simple classes on a non-local machine (a machine that throw errors when I try and use classes from my local machine)... and after registration they work perfectly (!) on my local machine. Interestingly classes I build on the non-local machine do not function of the excel version of the non-local machine.

So although not solved some progress. Going to check Excel versions across machines and that .NET frameworks are consistent.

cheers

Dave Kreskowiak23-Mar-07 13:26

23-Mar-07 13:26

LittleEd wrote:
o although not solved some progress. Going to check Excel versions across machines and that .NET frameworks are consistent.

My next two suggestions! Big Grin | :-D

Dave Kreskowiak
Microsoft MVP - Visual Basic

LittleEd26-Mar-07 5:09

26-Mar-07 5:09

OK think we are there ...

Client machines were looking to run (& debug) using a V1 release under NET. It was quite a pain finding how to amend this setting.

Tried editing the registry

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\AD7Metrics\Engine\{449EC4CC-30D2-4032-9256-EE18EB41B62B}

and adding & setting this entry:

CLRVersionForDebugging=V2.0.50727

..with no effect.

Stumbled upon a solution: edit (or create if necessary) excel.config.exe.xml file to look like

<configuration>
<startup>

<supportedruntime version="v2.0.50727">
<requiredruntime version="v2.0.50727">

& I placed a copy in the same dir as the excel.exe file. All COM classes now available, debugger works fine etc.

Should be *careful* on backward compatability issues but that's not a concern for me.

thanks for your interest,
GH
Laugh | :laugh:

LittleEd21-Mar-07 13:13

21-Mar-07 13:13

I should have added that i've tried to register the type library itself - the code ran fine but the still app didn't let me instantiate objects

the code I used was in the spirit of the link below
http://www.devx.com/vb2themax/Tip/18443

Smile | :)

MOD Operator

codemunkeh21-Mar-07 8:16

codemunkeh

21-Mar-07 8:16

OK, there doesn't seem to be a concise definition of this anywhere, particularly on MS's pathetic excuse for help.

With the Mod operator, I've always thought that it return everything after the decimal point. Eg,
12 / 5 = 2.4
Therefore I'd expect
12 Mod 5 = 4

In practice, the result seems to be a random number, dependant on the current temparature in Kelvin, the number of times you have double clicked in the last six seconds and a random number between 12 and 47. From some testing...

12 Mod 5 = 2 ?? Mad | :mad:

In fact, from the source code on MSDN, they say that
10 Mod 3 = 1

All I really need it for is working out if a Byte is even or not. If anyone can dare to explain, I'm sure it'll be useful.

Yet another spam post on yet another forum!
I am the lazy one, who sleeps as it suits him, codes what he wishes, and has many years to look forward to.
I love being a student.

Don Trainer21-Mar-07 8:25

Don Trainer

21-Mar-07 8:25

MOD Returns the remainder left over after the first number is divided by the second number

12/5 is 2 with a remainder of 2 Therefore 12 MOD 5 is 2

10/3 is 3 with a remainder of 1 Therefore 10 MOD 3 is 1

and so forth.

Don

codemunkeh21-Mar-07 8:30

codemunkeh

21-Mar-07 8:30

So it's the actual difference...dang. Been thinking in decimal too long. Well that was clever - especially since it's only taken me 3 years to notice...
Ooo...this could have new uses.

Thanks muchly.

Yet another spam post on yet another forum!
I am the lazy one, who sleeps as it suits him, codes what he wishes, and has many years to look forward to.
I love being a student.

Don Trainer21-Mar-07 8:34

Don Trainer

21-Mar-07 8:34

Yuppers such as a quick and dirty way to check to see if the current minute is a multiple of 5 without all the fancy if minute/5 = int(minute/5) and so forth. Use it for all sorts of cool stuff.

Glad to be of help...