0

Is there a way to specify a WSE3 proxy in the config file instead of code. I figured out how to get it working in code as follows: 

valservice.Proxy = new System.Net.WebProxy("http://10.192.xx.xx:8080", true);

Details: I have a WCF wrapper web service that is calling a WSE3 external vendor web service. The WSE3 code was working fine when called from a form, but not when running under IIS as another web service.

skaffman
  • 398,947
  • 96
  • 818
  • 769
NealWalters
  • 17,197
  • 42
  • 141
  • 251

1 Answers1

1

Any reason why you cannot use the normal appSettings for this?

See an example here.

Glorfindel
  • 21,988
  • 13
  • 81
  • 109
Wim
  • 11,998
  • 1
  • 34
  • 57
  • No, I was just guessing that there was a more standardized way to do it. In WCF, there seem to be XML for everything, but maybe not with WSE3? – NealWalters Nov 18 '09 at 16:09
  • So the Proxy was indeed the connectivity issue as per your previous question then, I take it? – Wim Nov 18 '09 at 16:11
  • Wim - Yes - http://stackoverflow.com/questions/1752646/unable-to-connect-to-the-remote-server/1757012#1757012 I put in my own answer there. – NealWalters Nov 19 '09 at 15:42