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
405k96 gold badges825 silver badges775 bronze badges
asked Nov 18, 2009 at 16:01
NealWalters
18.5k48 gold badges165 silver badges285 bronze badges
1 Answer 1
Any reason why you cannot use the normal appSettings for this?
See an example here.
Glorfindel
22.8k13 gold badges97 silver badges124 bronze badges
answered Nov 18, 2009 at 16:06
Wim
12.1k1 gold badge37 silver badges57 bronze badges
Sign up to request clarification or add additional context in comments.
3 Comments
NealWalters
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?
Wim
So the Proxy was indeed the connectivity issue as per your previous question then, I take it?
NealWalters
Wim - Yes - stackoverflow.com/questions/1752646/… I put in my own answer there.
default