R
Raghu
(Sorry for cross post but kinda in a hurry)
I have com+ server applicaiton on machine A. The exported application proxy
is installed on machine B. Both machines have windows 2003 os. Both machines
are configured to be application servers. I created on machine B:
1) A vbs file
2) VB.NET assembly
Both create the same component using CreateObject on machine B as shown
below:
Set x= CreateObject("Q.ITS.CHISWrapper")
The same code works in VBS file but fails in VB.NET assembly.
If I change the code in VB.NET to following:
Set x= CreateObject("Q.ITS.CHISWrapper", "machineA")
It works. However I should not have to do this because machine B has an
application proxy.
Any ideas?
Thanks.
Raghu/..
I have com+ server applicaiton on machine A. The exported application proxy
is installed on machine B. Both machines have windows 2003 os. Both machines
are configured to be application servers. I created on machine B:
1) A vbs file
2) VB.NET assembly
Both create the same component using CreateObject on machine B as shown
below:
Set x= CreateObject("Q.ITS.CHISWrapper")
The same code works in VBS file but fails in VB.NET assembly.
If I change the code in VB.NET to following:
Set x= CreateObject("Q.ITS.CHISWrapper", "machineA")
It works. However I should not have to do this because machine B has an
application proxy.
Any ideas?
Thanks.
Raghu/..