Release PostSharp 2024.0.28 · postsharp/PostSharp.Public

PostSharp 2024.0.28 is based on v2024.0.27, plus the following changes.

#177 When an assembly fails to load because of an earlier request made before the project was loaded, PS0265 now shows the complete stack trace of the code that made that request, and the assembly resolution logs the requesting assembly.
#176 The new FileLock trace category (PostSharpTrace=FileLock) records the retries of file operations that fail because the file is locked: when they start, when the error changes, and how they end. Before, a lock shorter than the 5 seconds of the FileLock warning left no trace in the build log.
#178 The POSTSHARP_FILE_LOCK_TIMEOUT and POSTSHARP_FILE_LOCK_WARNING environment variables set the timeout and the warning threshold of the retries on locked files, in milliseconds. The defaults are unchanged: 10 seconds and 5 seconds.

#113 With VcsCheckEnabled, a project that applies no aspect, such as an aspect library, no longer fails with PS0242 when its source files are unmodified. The source control check now runs whether or not an aspect is woven.
#123 Fixed a RemotingException ("Object '…' has been disconnected or does not exist at the server") that failed the build when a weave did not communicate with the build for several minutes. The endpoint of the pipe server now stays reachable for as long as the weave runs.
#150 An assembly lookup through the host assembly store before build-time logging is initialized no longer makes every later lookup in the AppDomain fail.
#253 Fixed BindingException: Ambiguous assembly binding policies on .NET Framework when the project redirects an assembly that PostSharp ships to a newer version. The redirect of the project now replaces the redirect of PostSharp instead of being added next to it.
#245 The ARM64 native compiler host now queries the global assembly cache for the ARM64 variant of an assembly, instead of the x86 variant.

Navigation Menu