SystemBootUtility Class |
Utility used for "booting up" OIS.
What it does:
- Creates an AppIdentity
- Applies before-boot update commands
- Refreshes the memory cache
- Creates/updates xml schema data objects
- Computes approximate no. of data objects per DOT in the system
- Validates that configured code methods and access modifiers are valid
- Initializes event handler classes
- Applies after-boot update commands
Inheritance HierarchySystemObject
Omada.OE.AppLogicSystemBootUtility
Omada.OE.AppLogicSystemBootUtility
Namespace: Omada.OE.AppLogic
Assembly: Omada.OE.AppLogic (in Omada.OE.AppLogic.dll) Version: 15.0.0.0
SyntaxC#
public class SystemBootUtility
The SystemBootUtility type exposes the following members.
Constructors| Name | Description | |
|---|---|---|
 | SystemBootUtility |
SystemBootUtility constructor
|
Properties| Name | Description | |
|---|---|---|
 | BeforeBootUpdateActionWasExecuted |
Is true if any BeforeBootup update actions was actually executed (because they hadn't been so before).
|
| ConnStr |
Connection string for the customer DB.
|
| CustomerId |
Customer Id.
|
| Identity |
The identity that has been created on the thread.
|
| IgnoreNonPresentAssemblies |
Should we simply ignore registered code assemblies that can't be loaded because they aren't present on the harddrive?
|
| NeverSkipBootSteps |
Option is mainly intended for certain test classes.
If true we will never skip performing certain boot steps due to detecting that they have already been performed.
|
| SkipAccessModifierValidation |
Skip validating that all configured access modifiers map to existing .Net classes?
|
| SkipAllOptions |
Sets all "Skip" flags at the same time.
|
| SkipAppStringUpdate |
Skip updating master data appstrings (like property names) from the AppText files?
Option is used by the integration test library to speed things up a bit.
|
| SkipCodeMethodValidation |
Skip validating that all configured code methods map to existing .Net methods?
|
| SkipLogInitializationIfAlreadyConfigured |
If true, the logging API will not be re-initialized if the log has already been configured and initialized once.
This is mainly to avoid that the logging is re-initialized when the RoPE RemoteAPI is triggered.
|
| SkipUpdateActions |
If true we will skip checking for and running missing update actions
|
| SkipUpdatingApproxDataObjectCounts |
Skip computing an approximate no. of data objects per DOT?
|
| SkipUpdatingXmlSchemaFiles |
Skip creating/updating xml schema data objects based on xml schema files on the disk?
|
Methods| Name | Description | |
|---|---|---|
| Initialize(Int32) | |
| Initialize(String) |
Events| Name | Description | |
|---|---|---|
 | IdentityCreated |
Fires when the creation of the AppIdentity has been finalized.
|
| StepPerformed |
Fires when a step has been performed.
|
Extension Methods| Name | Description | |
|---|---|---|
 | ToBool |
Converts object to boolean.
(Defined by ObjectExtensions.) |
| ToDateTime |
Converts object to DateTime.
(Defined by ObjectExtensions.) |
| ToInt |
Converts object to integer.
(Defined by ObjectExtensions.) |
See Also