context.Services.GetInitLogger<AbpAspNetCoreModule>().LogWarning(ex,"Could not load the static web assets manifest, static web assets will not be available. This usually happens when the application runs with build output instead of publish output.");
// The file is truncated before the updated XML is written back, so a failure here
Logger.LogError(ex,"Failed to update central package versions in \"{FilePath}\".",filePath);
// (disk full, process killed, file locked mid-write) can leave it empty/partially
// written on disk. Logged as an error (not a warning) so this isn't missed - the
// rest of the switch-to-nightly run still continues for other solutions/files.
Logger.LogError(ex,"Failed to update central package versions in \"{FilePath}\". The file may now be empty or partially written - please check it manually.",filePath);