SAIF.Business.Utilities.vbproj declares no same-repo <ProjectReference> elements — this is a leaf/foundation library with no outbound in-repo project dependencies. Within this repository it is consumed (inbound) only by SAIF.Business.View.Policy, via <ProjectReference> and the project-level Import Include="SAIF.Business.Utilities". Its internal dependencies are the organizational SAIF NuGet packages below.
Dependency
Reference Type
Usage
SAIF.Framework.Common
NuGet Package
Supplies SAIF.Framework.Extensions helpers (ToStringAll, IsIn, TakeFromEnd) and SAIF.Framework.StandardFormats.PadCapitalLettersFormat used in TitleCase.vb*
The library declares several packages (SAIF.BOF.Framework components, Oracle.ManagedDataAccess, Newtonsoft.Json, RestSharp, SAIF.HashUtil, SAIF.Web.API.Clients/SAIF.Web.API.Core) that have no confirmed usage in the two hand-written source files — these are referenced but unused by this project's code*, representing unnecessary reference surface/risk.
No BOF framework base classes (BusinessObjectBase, BusinessCriteriaBase, Bindable*, etc.) are inherited anywhere in this library, despite the SAIF.BOF.Framework reference*.
TitleCaseExtensions and mdlTextConversion are Public Modules, so importing the SAIF.Business.Utilities namespace silently injects several extension methods onto String/String() in any consuming project — a wide ambient surface that is a notable coupling risk*.
The nested Tests/Tests.vbproj (MbUnit) is not included in LegalMaintenance.sln, so the documented casing contract is not verified by the repository build*.