Dual Web Service References

[Fred Chateau]

I have a UI application that references business objects in Visual Studio on
two identical servers (ws1 & ws2). The business objects are the same so the
methods from each Web Service proxy are the same. I instantiate each Web
Service proxy in the application and call the methods but the methods are
always answered from ws1.

Is this a bug in Visual Studio or must each Web Service proxy contain
uniquely named methods?

The following is code from the application:

--
<applicationSettings>
<DataManager.Properties.Settings>
<setting name="DataManager_ws1_DataAdministrator" serializeAs="String">
<value>http://ws1.domainname.com/DataAdministrator.asmx</value>
</setting>
<setting name="DataManager_ws2_DataAdministrator" serializeAs="String">
<value>http://ws2.domainname.com/DataAdministrator.asmx</value>
</setting>
</DataManager.Properties.Settings>
</applicationSettings>

--
DataManager.ws1.DataAdministratorSoap admin1 =
new DataManager.ws1.DataAdministratorSoap();
DataManager.ws2.DataAdministratorSoap admin2 =
new DataManager.ws2.DataAdministratorSoap();

--
Regards,

Fred Chateau
fchateauAtComcastDotNet

[Pablo Cibraro [MVP]]

Hi Fred,

If the web services are identical, there is not reason to have two different
proxy classes on the client side. You can have only one proxy (You add the
web service reference once), and set the right URL before using it.

For example,

DataManager.ws.DataAdministratorSoap admin1 = new
DataManager.ws.DataAdministratorSoap();
admin.Url = http://ws1.domainname.com/DataAdministrator.asmx";

DataManager.ws.DataAdministratorSoap admin2 = new
DataManager.ws.DataAdministratorSoap();
admin.Url = http://ws2.domainname.com/DataAdministrator.asmx";
Regards,
Pablo Cibraro.

"Fred Chateau" <fc******@127.0.0.1wrote in message
news:eg**************@TK2MSFTNGP03.phx.gbl...

>I have a UI application that references business objects in Visual Studio
on two identical servers (ws1 & ws2). The business objects are the same so
the methods from each Web Service proxy are the same. I instantiate each
Web Service proxy in the application and call the methods but the methods
are always answered from ws1.

Is this a bug in Visual Studio or must each Web Service proxy contain
uniquely named methods?

The following is code from the application:

--
<applicationSettings>
<DataManager.Properties.Settings>
<setting name="DataManager_ws1_DataAdministrator" serializeAs="String">
<value>http://ws1.domainname.com/DataAdministrator.asmx</value>
</setting>
<setting name="DataManager_ws2_DataAdministrator" serializeAs="String">
<value>http://ws2.domainname.com/DataAdministrator.asmx</value>
</setting>
</DataManager.Properties.Settings>
</applicationSettings>

--
DataManager.ws1.DataAdministratorSoap admin1 =
new DataManager.ws1.DataAdministratorSoap();
DataManager.ws2.DataAdministratorSoap admin2 =
new DataManager.ws2.DataAdministratorSoap();

--
Regards,

Fred Chateau
fchateauAtComcastDotNet

[Fred Chateau]

"Pablo Cibraro [MVP]" <pc******@hotmail.comwrote ...

If the web services are identical, there is not reason to have two
different proxy classes on the client side. You can have only one proxy
(You add the web service reference once), and set the right URL before
using it.

Apparently there's a good reason to have only one proxy. The application
works using your suggestion.

Thanks.

--
Regards,

Fred Chateau
fchateauAtComcastDotNet