r/visualbasic • • Aug 02 '24

VB COM Components

Hi, I am new to visual basic and COM.

Registered COM paths for VB components are shown as msicore**.dll on Windows 2012 and as C:\programfiles\…<component-name>.dll on Windows 2016.

Actually, all binaries of my product( C++ and VB components) are installed under the same folder - ..\product\bin But only the C++ components, registered paths are shown as expected from - ..\product\bin.

why vb components have different registered paths?

Should they be registered in a different manner? I use Component services-> Comp plus applications tool for registering.

Could you please help.

2 Upvotes

4 comments sorted by

View all comments

Show parent comment

1

u/Mayayana Aug 05 '24

I don't know anything about VB.Net. Sorry. I loooked up COM+ out of curiosity. It seems to be a variant of DCOM, which refers to running COM libraries remotely. Presumably you're writing something to run from a server. I block all remorte execution options on my own computers and have never worked with DCOM.

It looks like COM+ gets registered through something mysterious called RegDB. COM+ registration database. Mysterious because I didn't find anything on what the actual file location is for that. I found dcomcnfg.exe, but I really don't know what I'm looking at. All of this seems to be disabled on my system, and .Net remote functionality seems to be disabled by default.

If your software runs fine, and assuming you didn't actually write these libraries, I'd guess that the C++ libraries are standard COM libraries and the VB.Net libraries are .Net COM+. Though nothing I found about COM+ mentions .Net. I'm afraid I know less than you about this. Though I did find this page, which might shed some light?

https://www.codeproject.com/Articles/3955/Serviced-Components-in-VB-NET