by Kelvi » Wed, 10 Jul 2002 11:52:58
I have written a VB.NET dll running on an application
server. For .NET remote clients, they can access the
component through web service or remoting. But how can VB6
remote client access the component?
Can anyone help me with this? I've spend a long time
scanning through this user group and couldn't find the
solution.
Thanks a lot!
Kelvin
by Kumar Gaurav Khann » Wed, 10 Jul 2002 14:27:28
I suggest that you register the TLB on the client machines, and try
configuring the component instantiation using DCOMCNFG.
--
"French is the language of love, C# is for everything else..."
Kumar Gaurav Khanna
Early Achiever MCSE Windows 2000, MCSE NT 4.0, MCP+I
WWW: http://www.wintoolzone.com/
Quote:> Hi all,
> I have written a VB.NET dll running on an application
> server. For .NET remote clients, they can access the
> component through web service or remoting. But how can VB6
> remote client access the component?
> Can anyone help me with this? I've spend a long time
> scanning through this user group and couldn't find the
> solution.
> Thanks a lot!
> Kelvin
by PixPe » Wed, 10 Jul 2002 23:14:32
If your .Net component is a web service you can use it
from a remote machine using SOAP. Check for the SOAP
toolkit 2.0 for more details.
When you use a Web-reference on a .Net project this is
made automaticaly .. but on a VB 6.0 you have to do it
manually.
PixPex
Quote:>-----Original Message-----
>Hi all,
>I have written a VB.NET dll running on an application
>server. For .NET remote clients, they can access the
>component through web service or remoting. But how can
VB6
>remote client access the component?
>Can anyone help me with this? I've spend a long time
>scanning through this user group and couldn't find the
>solution.
>Thanks a lot!
>Kelvin
>.
by Kelvi » Thu, 11 Jul 2002 11:26:15
Many Thanks!
Kelvin
>I suggest that you register the TLB on the client
machines, and try
>configuring the component instantiation using DCOMCNFG.
>--
>"French is the language of love, C# is for everything
else..."
>Kumar Gaurav Khanna
>Early Achiever MCSE Windows 2000, MCSE NT 4.0, MCP+I
>WWW: http://www.wintoolzone.com/
>> Hi all,
>> I have written a VB.NET dll running on an application
>> server. For .NET remote clients, they can access the
>> component through web service or remoting. But how can
VB6
>> remote client access the component?
>> Can anyone help me with this? I've spend a long time
>> scanning through this user group and couldn't find the
>> solution.
>> Thanks a lot!
>> Kelvin
>.
1. Calling IDL experts - IDL from .NET COMponents vs. IDL from VB6 components
Hi
Having created 2 COMponents (one in VB6 and one in VB.NET) I have a VB6
client that uses them and in the object browser (and intellisense they are
identical) so I expected their IDL (when viewed in OleView) to be identical
as well (except for the guids of course)...
There are 4 differences:
1) In the IDL for the VB6 created dll all default (inc. source) interfaces
have the hidden attribute (whereas the .NET counterparts do not).
2) In the IDL for the VB6 created dll all interfaces have the nonextensible
attribute (whereas the .NET counterparts do not).
3) In the IDL for the VB6 created dll one interface had some [restricted]
entries (whereas the .NET counterparts did not).
4) In the IDL for the .NET created dll all elements have a custom attribute
(whereas the VB6 counterparts do not).
Can anybody explain these given that, as I said, the VB6 client object
browser displays them as *identical*.
Cheers
Daniel
PS Examples of above:
1) & 2) & 3)
[
odl,
uuid(F09F00EE-B2BD-4F1D-B44F-79380A6E8D5C),
version(1.0),
hidden,
dual,
nonextensible,
oleautomation
]
interface _MyCoClass : IDispatch {
[restricted] void Missing7();
[restricted] void Missing8();
[restricted] void Missing9();
[id(0x68030000), propget]
HRESULT MeAsIMyInterface([out, retval] _IMyInterface** );
4)
[
odl,
uuid(40AA52BC-620D-471B-9FAE-F223EA36FB6F),
version(1.0),
dual,
oleautomation,
custom(0F21F359-AB84-41E8-9A78-36D110E6D2F9, CalledViaCom._MyCoClass)
]
interface _MyCoClass : IDispatch {
[id(0x00000001), propget]
HRESULT MeAsIMyInterface([out, retval] IMyInterface** pRetVal);
};
2. timing test
3. VB6 remote client try to access .NET component on server
4. Installing HP LaserJet 4M on Solaris...
5. Is it possible that a VB6 applicatin can call components created by .Net?
6. Thank you microsoft for osr2
7. VB6 to .NET C# component call
8. Inserting DoubleQuotes using Placeholders
9. Using / Calling a Visual Component (C# or .NET) from VB6 - Activex / COM wrapper
10. Debugging VB6 COM objects called by .NET components?
11. Calling .Net Component from VB6 client
12. Calling a VB6 COM+ Component from .NET
13. Calling remote DCOM server (Unmanaged Classic COM Component) from .NET client