A cached version of the WebMetadata class for deployment on a server. It is read-only and will not flush any changes to the disk file(s).

For a list of all members of this type, see WebMetadataCache Members.

System.Object
   Parastream.Web.MsFrontPage.WebMetadataCache

Thread Safety

Public static (Shared in Visual Basic) members of this type are safe for multithreaded operations. Instance members are not guaranteed to be thread-safe.

Remarks

Normally the cache is associated with two files, named _vti_pvt/service.cnf and _config/service.cnf. If either of these files has been modified since the cache was loaded, the cache is flushed and reloaded from whichever file has been modified most recently.

While this is optimal for web projects managed by both FrontPage and PagePorter. NET, it isn't the most efficient for web projects managed by PagePorter alone. This class supports a setting in the configuration file that can indicate whether or not to look for the FrontPage file _vti_pvt/service.cnf. If you add the following example to your web.config file, the FrontPage file will be ignored, and will associate only with the PagePorter file _config/service.cnf:

    <configuration>
          ...
      <configSections>
        <sectionGroup name="Parastream.PagePorter">
          <section name="Application"
                   type="System.Configuration.NameValueSectionHandler, System, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, Custom=null" />
        </sectionGroup>
      </configSections>

      <Parastream.PagePorter>
        <Application>
          <add key="IncludeFrontPageWeb" value="0" />
        </Application>
       </Parastream.PagePorter>
          ...
    </configuration>
    

Put the <configSections> as shown above before the main <system.web> section.

Requirements

Namespace: Parastream.Web.MsFrontPage

Assembly: FpCtrlsBase (in FpCtrlsBase.dll)

See Also

WebMetadataCache Members | Parastream.Web.MsFrontPage Namespace

---