Hongye Sun

Submit button unexpected postback in WebBrowserControl

hongyes — Thu, 26 Mar 2009 23:21:09 GMT

Originally posted on: http://geekswithblogs.net/hongyes/archive/2009/03/26/submit-button-unexpected-postback-in-webbrowsercontrol.aspx

In .NET, When you add an event handler to any of the predefined events in HtmlDocument of WebBrowserContro.Document, it will register a default event handler for all the other events.

If the submit button has an onclick javascript event handler. The javascript returns false to prevent the page to postback. However, return false will not work properly if there is another event handler registered. Instead of returning false, the best choice in the HTML page is to set event.returnValue = false.

Another workaround is to change your .NET code, use AttachEventHandler method instead:

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click

doc = webBrowserControl.Document

doc.AttachEventHandler("onclick", AddressOf oDoc.OnClick)

End Sub

Remove Handles doc.Click in your code.

Visual Studio Tip: Navigate to File by Typing File Name

hongyes — Mon, 23 Mar 2009 22:55:49 GMT

Originally posted on: http://geekswithblogs.net/hongyes/archive/2009/03/23/visual-studio-tip-navigate-to-file-by-typing-file-name.aspx

In Visual Studio, press CTRL+D, type ">of <FileName>", replace <FileName> with real file name.

Visual Studio can also list all possible files for you.

TFS Error: The process cannot access the file ProxyStatistics.xml

hongyes — Fri, 13 Mar 2009 01:59:25 GMT

Originally posted on: http://geekswithblogs.net/hongyes/archive/2009/03/12/tfs-error-the-process-cannot-access-the-file-proxystatistics.xml.aspx

Recently my customer encounters the following errors in TFS 2005:

Exception Message: The process cannot access the file 'X:\Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\VersionControl\App_Data\ProxyStatistics.xml' because it is being used by another process. (type IOException)

Finally, we found that it is because that TFS application pool in IIS is configured to use multiple worker processes. Please configure it back to 1 to solve this problem.