Scenario: An ASP+ Page written in a NGWS runtime managed language (VB7) and updates multiple databases. The managed page is hosted in an ASP+ Worker process.
ASP+ supports the following Transaction directives for use on pages. The level of transaction support for the page is indicated with a Transaction directive, as shown in the following example:
<@% Transaction=”Required” %>
The default transaction state is none, which indicates that the transaction context will be ignored by the ASP+ framework. There is no explicit directive for none (e.g. Transaction=”None”) since the absence of the directive indicates this.
Transaction directive
Directive | Explanation |
---|---|
Required | The page requires a transaction. It will run in the context of an existing transaction, if one exists. If not, it will start one. |
Requires_New | The page requires a transaction and a new transaction will be started for each request. |
Supported | The page will run in the context of an existing transaction, if one exists. If not, it will run without a transaction. |
Not_Supported | This value indicates that the page does not run within the scope of transactions. When a request is processed, its object context is created without a transaction, regardless of whether there is a transaction active. |