|
-
February 9th, 2000, 07:10 AM
#1
VB accessing a DCOM interface
I have a service (VC++) which exposes a COM interface. When I register the proxy stub on a client machine it does not register a ProgID.
Is the a build setting to make this happen. Otherwise, how can I get a VB app to access this interface given only the GUID and not a ProgID ?
Brendan Baird
-
March 1st, 2000, 04:56 PM
#2
Re: VB accessing a DCOM interface
I have the same question, anyone can help us out?
-
March 7th, 2000, 12:49 PM
#3
Re: VB accessing a DCOM interface
perhaps a call to the function ProgIDFromCLSID defined in the ole32.dll
just an idea!
-
March 7th, 2000, 06:24 PM
#4
Re: VB accessing a DCOM interface
Yes, you will need to use ProgIDFromCLSID from ole32.dll, but you cant access this interface with early bound without the use of other com interface functions.
the QueryInterface is the aswer for your problem but in vb is very boring to do this.
The use of late bound references is more simple.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|