 <p>The approach being described in the post you linked is to use the <code>WebBrowser</code> control's <code>InvokeScript</code> method to run some javascript. However the post appears to use a "cookies" collection which doesn't actually exist.</p> <pre><code> string cookie = myWebBrowser.InvokeScript("document.cookie") as string; </code></pre> <p>Now for the hard part the string you get contains all pertinent cookie name/value pairs for the page with the values still being Url encoded. You will need to parse the returned string for the value you need.</p> <p>See <a href="http://msdn.microsoft.com/en-us/library/ms533693%28v=VS.85%29.aspx" rel="nofollow">document.cookie property</a> documentation.</p> <p><strong>Edit</strong>:</p> <p>Looking at it fresh instead of relying on the post, <code>InvokeScript</code> invokes named function on the window of the host browser. Hence the page being displayed in the WebBrowser would itself need to include a function like:-</p> <pre><code> function getCookie() { return document.cookie; } </code></pre> <p>Then the <code>InvokeScript</code> would look like:-</p> <pre><code> string cookie = myWebBrowser.InvokeScript("getCookie"); </code></pre>