title: HttpWebRequest socket operation during WPF binding in a property getter
body: <p>In a property getter of a C# class I am doing a <code>HTTP GET</code> using <code>HttpWebRequest</code> to some https address. WPF's property binding seems to choke on this. If I try to access the property in a simple method e.g. <code>Button_Clicked</code>, it works perfectly. If I use WPF binding to access the same property, the app seems to be blocked on a socket's <code>recv()</code> method indefinitely.</p>
  
  <p>Is it a no-no to do this sort of thing during binding? Is app in some special state during binding?</p>
  
  <p>Is there an easy way for me to overcome this limitation and still maintain the same basic idea?</p>