DP44/docs/ai/DataPRO/Modules/InstallerCustomActions/LocalSQLDB/Properties.md

source_files, generated_at, model, schema_version, sha256

source_files	generated_at	model	schema_version	sha256
DataPRO/Modules/InstallerCustomActions/LocalSQLDB/Properties/AssemblyInfo.cs DataPRO/Modules/InstallerCustomActions/LocalSQLDB/Properties/Settings.Designer.cs	2026-04-17T16:13:20.075967+00:00	zai-org/GLM-5-FP8	1	1f2e29b6af979ed1

Properties

Purpose

This module provides assembly metadata and application-scoped configuration settings for the LocalSQLDB custom installer action. It exists to configure file paths, extensions, and registry keys related to local SQL Database deployment for the DataPRO application. The settings support the installer's ability to locate and configure local database files during installation.

Public Interface

• Settings class (internal sealed, partial) - Auto-generated settings class inheriting from System.Configuration.ApplicationSettingsBase.
  • static Settings Default { get; } - Returns the synchronized singleton instance of settings.
  • string RegistryDataPROExe { get; } - Returns "DataPRO.exe". Application-scoped setting.
  • string ApplicationSettings { get; } - Returns "applicationSettings". Application-scoped setting.
  • string LocalDbFolder { get; } - Returns "db". Application-scoped setting.
  • string Mdf { get; } - Returns ".mdf". SQL Server primary database file extension. Application-scoped setting.
  • string LogLdf { get; } - Returns "_log.ldf". SQL Server log file suffix/extension. Application-scoped setting.
  • string DataPRO { get; } - Returns "DataPRO". Application-scoped setting.

Invariants

• All settings are application-scoped and read-only at runtime.
• File extension settings (Mdf, LogLdf) must include the leading dot where appropriate (.mdf does, _log.ldf includes prefix).

Dependencies

• Depends on: System.Configuration.ApplicationSettingsBase, System.Runtime.CompilerServices, System.Runtime.InteropServices.
• Depended on by: The parent LocalSQLDB installer custom action module (inferred from namespace).

Gotchas

• The LogLdf setting value is "_log.ldf" which includes a prefix underscore, not just the extension. This suggests it's meant to be appended to a database name, not just a pure extension.
• The RegistryDataPROExe setting name suggests registry usage, but the value is just a filename without a path.

---