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.");
// LeptonX and Studio packages follow their own, independent version
{
// stream (see IsLeptonXPackage/IsStudioPackage, also used by
Logger.LogInformation("Updating central package \"{PackageId}\" from v{CurrentVersion} to v{LatestVersion}",packageId,versionAttribute.Value,latestVersionFromMyGet);
// UpdateVoloPackagesAsync above) - never stamp them with the
versionAttribute.Value=latestVersionFromMyGet;
// Volo.Abp.Core anchor version, regardless of --exclude-packages.
Logger.LogInformation("Updating central package \"{PackageId}\" from v{CurrentVersion} to v{LatestVersion}",packageId,versionAttribute.Value,latestVersionFromMyGet);
awaitsw.FlushAsync();
versionAttribute.Value=latestVersionFromMyGet;
}
}
}
}
}
}
varupdatedXml=doc.OuterXml;
// Write to a temp file in the same directory and atomically swap it in with
// File.Replace, instead of truncating filePath in place - this way a failure
// mid-write (disk full, process killed) never leaves the original file empty
// or partially written; it either stays untouched or is fully replaced.
// 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);