By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,524 Members | 1,330 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,524 IT Pros & Developers. It's quick & easy.

Same code in VBS file and VB.NET Assembly - VBS works but VB.NET fails

P: n/a
(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/..


Nov 21 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Failed to mention that the com+ server application was written in C#.

"Raghu" <Ra***@Nospam.com> wrote in message
news:u#*************@TK2MSFTNGP09.phx.gbl...
(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/..

Nov 21 '05 #2

P: n/a
Failed to mention that the com+ server application was written in C#.

"Raghu" <Ra***@Nospam.com> wrote in message
news:u#*************@TK2MSFTNGP09.phx.gbl...
(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/..

Nov 21 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.