The Application context object holds information that is used throughout each page (or server) request. The Application is available to all objects, either as a direct parameter or property on an existing object. The Application object is created as the first object in any request, and when possible it is cached for performance purposes.

Namespace: NetQuarry
Assembly: EAP.Core (in EAP.Core.dll) Version: (


public interface IAppContext : IEAPBase, 
Visual Basic
Public Interface IAppContext
	Inherits IEAPBase, IDisposable


The Application object handles connecting to the authentication provider, authenticating the user, checking object permissions for that user, storing user (UserContext) information, holding the list of available PageInfo objects, and connecting to the metadata (Repository) data source. It also has a collection of DataSources specified in metadata.

Application Load

An application is loaded in the following sequence:

  1. Configuration properties are loaded from the running application's configuration file. In the web, this file is web.config. In the studio, this file is EAP.Tools.exe.config. The configuration settings must have the named connection strings that will be used in the application.
  2. The repository database is opened (see OpenRepository(String, Properties)).
  3. The application's ID is set (optional). If there is no ID set, the default application configured in the repository is used.
  4. Init()()()() is called. During Init, the TextItems, Properties, Versions, Extensions, and Related Data Sources are loaded.
  5. The IAuthenticationProvider is determined from Application properties and an instance is created.
  6. The ApplicationBeforeAuthenticate event is fired.
  7. The configured Authentication provider's IAuthenticationProvider method is called to authenticate the user and load the user's profiles.
  8. The ApplicationAfterAuthenticate event is fired.
  9. The Load()()()() method is called to load the PageInfo and Navigator objects into the PageInfos and Navigators collections respectively. Pages and navigators respect the permissions of the authenticated user.
  10. The ApplicationAfterLoad event is fired.

See Also