Use this tab to install and register client and server components. You can also add a server component to the Microsoft® Transaction Server Library package.
Note File properties are read-only while you are offline. To change these settings, you must be connected to the network.
Registering client components such as ActiveX® controls and Java applets allows you to add these control to Web pages and access properties for these controls efficiently.
Register on client
Specifies that the file should be registered on the developer's machine. This option is available for .ocx, .dll, .cab, .jar, .exe, and .inf files.
Server component registration is supported for Intel or Alpha servers that have both Microsoft® Internet Information Server and the Microsoft® FrontPage® Server Extensions installed. Users must have permission to update the registry on the master Web server or local Web server in order to register server components successfully.
Register on server
Select to specify that the file should be installed and registered on the master Web server or local Web server whenever the master Web server or local Web server receives an updated copy of the file. This option is available for Active Server objects, such as .ocx, .dll, or project output files.
Add to Microsoft Transaction Server package
Select to specify that the file is added to the Microsoft Internet Information Server transaction library.
Package name
Select to specify the name of the Microsoft Transaction Server package to add .dlls to. This option is not available for .ocx files. To view the available Microsoft Transaction Server packages, launch Microsoft Management Console and find MTS/My Computer/Packages installed on the Web server.
Requires a transaction
Select to specify that Microsoft Transaction Server should start a new transaction for the page. The following tag is added to the top of all ASP pages in the Web project:
<%@ Transaction=required%>
Note Transaction processing applies only to database access; Microsoft Transaction Server cannot roll back changes to the file system or changes to other, non-transactional resources. A change that is being managed by transaction services can be either committed, making it more or less permanent, or aborted, which would result in the state of the database or queue being rolled back to before the changes were made.
For more information, see "Creating Transactional Scripts" in the Internet Information Server documentation.
Requires a new transaction
Select to specify that Microsoft Transaction Server should start a new transaction for the page. The following tag is added to the top of all ASP pages in the Web project:
<%@ Transaction=requires_new%>
Supports transactions
Select to specify that Microsoft Transaction Server should not start a transaction for the page. The following tag is added to the top of all ASP pages in the Web project:
<%@ Transaction=supported%>
Does not support transactions
Select to specify that Microsoft Transaction Server should not start a transaction for the page. The following tag is added to the top of all ASP pages in the Web project:
<%@ Transaction=not_supported%>