BUG: WebClass ProcessTag event fails to execute (279409)
The information in this article applies to:
- Microsoft Visual Basic Learning Edition for Windows 6.0
- Microsoft Visual Basic Professional Edition for Windows 6.0
- Microsoft Visual Basic Enterprise Edition for Windows 6.0 SP4
This article was previously published under Q279409 SYMPTOMS
When you run a WebClass project from within Visual Basic 6.0 Service Pack 4, and there is more than one WebClass tag in a Web document, the WebClass ProcessTag events may fail to execute. This does not occur if you browse the Active Server Pages (ASP) page directly.
CAUSE
This problem occurs if the previous execution of the ProcessTag event did not change the value of the TagContents variable. If your ProcessTag event never sets or modifies the value of the TagContents variable, every other tag is skipped.
RESOLUTION
To resolve this problem, while you are developing the WebClass project from within Visual Basic, set or modify the value of the TagContents variable every time the ProcessTag event executes. To do this, add the following line at the beginning of your ProcessTag event:
TagContents = TagContents
This line can be commented out or removed when the Web project is put into production, but it must be put back next time you run the WebClass project from within Visual Basic.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. REFERENCESFor additional information, click the article numbers below
to view the articles in the Microsoft Knowledge Base:
192035 PRB: Do Not Use a WebClass ProcessTag Inside an HTML Tag
234317 FIX: HTML Page Truncated with Visual Studio SP3 WebClass Run Time when Running in the VB IDE
For more information on sample Visual Basic projects, see the following MSDN article:
Modification Type: | Minor | Last Reviewed: | 10/1/2004 |
---|
Keywords: | kbBug kbEvent kbpending kbtemplate kbWebClasses KB279409 |
---|
|