.NET Help

  • Thread starter Thread starter Ravindra Garikapati
  • Start date Start date
R

Ravindra Garikapati

Hi all,
It would be very much helpful to me if you post or email an answer to
the following question.

Here is the requirement and I need an approach with regards to this.

I have java web services which exposes certain APIs. These services
are running on APACHE AXIS 1.1. We need to build a .NET component as a
middle layer which communicates with these web services. This .NET
commponent should be used in VC++ 6.0 applications.

The approach we followed in this case was
1. Depoly the Java web service.
2. Create class library in .NET which communicates with the web
service.
Output is the DLL.
3. Use regasm.exe to register and create the type library [ tlb ].
4. Import the type library into VC++ application.

This works in case .NET framework is installed on the client machine.
I have got 5000 machines on which this VC++ application will be
running on.
I do not want to install .NET framework on each and every client
machine.

Please reply back or mail me in case you have different approach or go
away with installation of .NET framework on client machines.

Regards,
Ravindra
 
Hi,

Honestly, I don't think it's wrong to install .NET on the client PCs -
eventually, almost every PC will have it installed soon - well, unless
there's some policy that advocates against it in your case.

You could of course make the .NET component a web service as well, and then
consume the web service from the VC++ 6.0 with the SOAP SDK, but this would
obviously require network (HTTP to be exact) connectivity to the box the
..NET web service resides on.
 
I am not sure it will work, because I never tried, but try DCOM.
After you register your .NET class, it becomes a COM server and may be
called through DCOM as well.
To call a COM object from a remote client
- use CoCreateInstanceEx specifying the computer name (see documentation in
MSDN),
or
- create a reg file using regasm, run it on remote computer, use dcomcnfg to
configure the object to run on a remote computer. Implement your COM client
as you would do it locally.
 
I guess implementing a web service client in VC 6.0 is exactly what they
would like to avoid by all those manipulations.


Dmitriy Lapshin said:
Hi,

Honestly, I don't think it's wrong to install .NET on the client PCs -
eventually, almost every PC will have it installed soon - well, unless
there's some policy that advocates against it in your case.

You could of course make the .NET component a web service as well, and then
consume the web service from the VC++ 6.0 with the SOAP SDK, but this would
obviously require network (HTTP to be exact) connectivity to the box the
.NET web service resides on.

--
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://x-unity.miik.com.ua/teststudio.aspx
Bring the power of unit testing to VS .NET IDE

Ravindra Garikapati said:
Hi all,
It would be very much helpful to me if you post or email an answer to
the following question.

Here is the requirement and I need an approach with regards to this.

I have java web services which exposes certain APIs. These services
are running on APACHE AXIS 1.1. We need to build a .NET component as a
middle layer which communicates with these web services. This .NET
commponent should be used in VC++ 6.0 applications.

The approach we followed in this case was
1. Depoly the Java web service.
2. Create class library in .NET which communicates with the web
service.
Output is the DLL.
3. Use regasm.exe to register and create the type library [ tlb ].
4. Import the type library into VC++ application.

This works in case .NET framework is installed on the client machine.
I have got 5000 machines on which this VC++ application will be
running on.
I do not want to install .NET framework on each and every client
machine.

Please reply back or mail me in case you have different approach or go
away with installation of .NET framework on client machines.

Regards,
Ravindra
Click to expand...
Click to expand...
 
Well, You can also implement a SOAP client with VC.NET 2003 without
using any managed classes but using ATL. That will also work.

I guess implementing a web service client in VC 6.0 is exactly what they
would like to avoid by all those manipulations.


Hi,

Honestly, I don't think it's wrong to install .NET on the client PCs -
eventually, almost every PC will have it installed soon - well, unless
there's some policy that advocates against it in your case.

You could of course make the .NET component a web service as well, and
then

consume the web service from the VC++ 6.0 with the SOAP SDK, but this
would

obviously require network (HTTP to be exact) connectivity to the box the
.NET web service resides on.

--
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://x-unity.miik.com.ua/teststudio.aspx
Bring the power of unit testing to VS .NET IDE

Hi all,
It would be very much helpful to me if you post or email an answer to
the following question.

Here is the requirement and I need an approach with regards to this.

I have java web services which exposes certain APIs. These services
are running on APACHE AXIS 1.1. We need to build a .NET component as a
middle layer which communicates with these web services. This .NET
commponent should be used in VC++ 6.0 applications.

The approach we followed in this case was
1. Depoly the Java web service.
2. Create class library in .NET which communicates with the web
service.
Output is the DLL.
3. Use regasm.exe to register and create the type library [ tlb ].
4. Import the type library into VC++ application.

This works in case .NET framework is installed on the client machine.
I have got 5000 machines on which this VC++ application will be
running on.
I do not want to install .NET framework on each and every client
machine.

Please reply back or mail me in case you have different approach or go
away with installation of .NET framework on client machines.

Regards,
Ravindra
Click to expand...
Click to expand...
Click to expand...
 
Back
Top