Supplies clsMenuAuthorizedItem / clsMenuAuthorizedItemCollection (menu item, favorite, and category data with authorization filtering) consumed throughout SAIFMenu and SAIFMenuTop.
Imports SAIF.Framework.Security used in SAIFMenu.vb*; SAIF.Framework.Preferences reference present in the project but no direct type usage found in the two source files (may be consumed transitively via SAIF.Presentation.clsPreferences)**. (v1.0.20105.1)
SAIF.Framework.Common
NuGet Package
Referenced at project level; no direct type usage identified in the analyzed .vb files**. (v1.0.18145.1)
SAIF.HashUtil
NuGet Package
Referenced at project level; no direct type usage identified in the analyzed .vb files**. (v1.0.18067.1)
The dependency on SAIF.Presentation.Web.Controls.V2 could not be confirmed as an actual compile-time type dependency versus a transitive/organizational-only reference; its removal impact is unclear**.
AppGlobal.EnvironmentService.IsClientExternal (used in SAIFMenu.AddFavorites to gate the "Change Password" favorite link) could not be traced to a specific referenced assembly within this library's scope; it is likely supplied by SAIF.Framework/SAIF.Framework.Common*.
SAIF.Framework.Common and SAIF.HashUtil are declared as both project-level references and .nuspec package dependencies, but no direct type usage was identified in this library's analyzed source — they may be transitive-only dependencies retained for packaging/versioning consistency**.
The Imports SAIF.Framework.Security statement in SAIFMenu.vb has no identifiable directly-referenced type in the visible source; it may be vestigial or used implicitly through inherited/extension behavior*.
Runtime coupling to ViewPageBase (SAIF.Presentation.Web.MVC) means these controls only function correctly on pages deriving from that base type; this is an architectural/interaction constraint rather than a build dependency, and is not restated as a separate row here (see Architecture).
This library consumes SAIF.Business.Menu's menu-authorization data as-is; that dependency library owns its own security/authorization model for menu items, which is not duplicated in this library's documentation set — see Architecture for the boundary note.
No transitive custom/internal dependencies beyond those already listed as internal or external above were identified from the analysis.
No /Pipelines folder exists in this repository snapshot, so pack-method and CI/CD dependency chain details could not be confirmed**.
Note: Statements marked with * were inferred from code structure, naming conventions, or
contextual evidence where direct confirmation was not available in source artifacts. Statements
marked with ** could not be confirmed; treat as unknown until verified.