TextEmbedParser object

This object implements pluggable parser architecture. It is used internally in ASP Compiler and also supplies some methods that could be useful when the object is used with or without ASP Compiler. For example:

In ASP Compiler the compile time scripts attached to a project file (or files) are able to instruct ASP Compiler to extract additional tags/parts of an HTML or ASP page by modifying the parser configuration. They are asked to do this through the OnModifyParser event.

Outside the ASP Compiler the object could be used for variety of purposes - as powerful HTML template tool, to extract specific information from HTML pages or collecting keywords and other details from a number of pages. 

This page explains only the features of common use. The features specific for ASP Compiler and used internally are not documented because they are used only internally. See these topics and examples for detailed information:

How to use it as HTML template tool (HTML object model parsing and reconstruction)

How to use the parser to extract specific information from HTML/ASP

Using in compile time scripts.

And also consult the members reference:

ParseString - Creates the object model tree of the string passed. Uses the currently configured parsers.

AddTag - Adds parser (sub-parser) for the HTML tag specified.

GenerateDoc - Generates HTML file from object model tree.

Program ID and Class ID:

Threading model: Both

ProgID: newObjects.utilctls.TextEmbedParser
ClsID: {7DB63A31-D42E-4953-9958-7BC2844D0850}

Threading model: Free

ProgID: newObjects.utilctls.TextEmbedParser.free
ClsID: {D478AE63-EAF1-4329-8DD0-717BA57AE609}

Most applications (recommended) should use the first IDs. They will create the object in the same threading model as the calling application. The second IDs are for special cases where free-threaded behavior is a requirement. For example on the IIS if the object will be kept in the Application or Session. Note that inappropriate usage of free-threaded model could cause decreased performance - use it only if it is a requirement or if your application is designed as free-threaded (many C++ server applications do).

The implementation of the parser is universal and in theory may cover anything from HTML/XML to programming language. The information on this page covers only a little part of its functionality. Internally the parser uses non-COM component architecture and could be extended with components in external DLLs. These features are currently reserved for the ASPC internal needs and we do not recommend any usage of features not listed here.