Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 309549 - Last Review: February 12, 2007 - Revision: 2.5
BUG: Visual Basic .NET or Visual Basic 2005 QuickStart TestClient.exe sample hangs on Windows NT 4.0
This article was previously published under Q309549
SYMPTOMS
When you run the Visual Basic .NET or Visual Basic 2005 QuickStart
TestClient.exe sample on Microsoft Windows NT 4.0, the sample stops responding
(hangs) before the page is loaded in Microsoft Internet Explorer.
The
TestClient.exe sample is located in the following folder:
..\Program Files\Microsoft Visual Studio .NET\
FrameworkSDK\Samples\QuickStart\Howto\Samples\Interop\Testclient_2\VB
Note In Visual Studio 2005, the TestClient.exe sample is located in the following folder:
..:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\QuickStart\howto\samples\interop\testclient_2\vb
CAUSE
This problem occurs because the
Console.Readline method does not pump messages on Windows NT 4.0 because of the
operating system implementation.
RESOLUTION
To resolve this problem, follow these steps:
- In TestClient.vb, locate the following line of code:
Imports System.Runtime.InteropServices
- In TestClient.vb, locate the following code and insert the following code after this line:
Thread.CurrentThread.Join()
- In TestClient.vb, remove the following section of code:
Console.WriteLine("Press Enter to quit")
Dim s As String = Console.ReadLine
Do While s <> ""
s = Console.ReadLine
Loop
- If you have the project open in Microsoft Visual Studio
.NET or Visual Studio 2005, on the Build menu, click Rebuild All.
Alternately, you can follow these steps to use Make
files to rebuild the project:
- From the Visual Studio .NET or from the Visual Studio 2005 command prompt, run the
nmake command to rebuild the TestClient.vb file in the
..\Testclient_2\VB directory.
- Run TestClient.exe to run the sample.
- To stop running the sample, close the browser window
manually, and press the CTRL+C key combination to free the command
window.
STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
APPLIES TO
- Microsoft Visual Basic .NET 2002 Standard Edition
- Microsoft Visual Basic .NET 2003 Standard Edition
- Microsoft .NET Framework 1.1
- Microsoft Visual Basic 2005 Express Edition
| kbvs2005applies kbvs2005swept kbvs2002sp1sweep kbbug kbpending kbreadme KB309549 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please