We have a custom logging framework used across all our applications and would ideally like to continue using this rather than switching to one of the ones supported by PostSharp. Is this currently possible, or is this an option for a future release?

The logging feature in PostSharp 5.0 is not designed for obfuscation. The idea is to make it obfuscation-friendly. Some problems to address are:

1. When type names are obfuscated, the hierarchy of namespaces (LoggingNamespaceSource) is lost.
2. Member names are not obfuscated.
3. Source files, lines and columns are not obfuscated.

Like for instance LogEventInfo in NLog.

NotifyPropertyChanged generates an unbearable overhead if the call count reaches millions of times.

Often the concerning properties are read-only (e.g. an ID), so wouldn't need PropertyChanged support at all.

I would like a way to opt out of PropertyChanged for individual properties.

I want to put assertions in my code like "must not have writer lock here".

It is crucial to know what lock is held in a certain situation.
When I apply attributes (Reader, Writer, ExplicitlySynchronized, Yielder) I make assumptions on what they will do, but there is no way to check my assumptions.

I tried using the IConcurrencyController.CheckAccess method, but it does not do what I need.

When you press F1 on any code from Microsoft, it takes you to the appropriate doc on MSDN. PostSharp can do the same with its types/methods/etc and doc.postsharp.net.

Instead of custom modification project files by install.ps1 (when installing NuGet package) use PostSharp.targets and PostSharp.properties from standard build folder in Nuget package.

The method OnSetValue() of the LocationInterceptionAspect isn´t called when you initialize your properties using auto-property initiliazers. This can be confusing because you expect that your aspect will be called if a property value is changed, no matter where and how.

This is more of a post for awareness, but it turns out that ReSharper's Build & Run does not integrate well with PostSharp's new and awesome Solution-Wide building. I have created an issue on JetBrains' side here:
https://youtrack.jetbrains.com/issue/RSRP-461793

It would be awesome to have these two working awesomely with one another! Thank you for any consideration.

Sometimes someone switches on the SkipPostSharp flag in a project, then a few months later, someone else adds some aspect to this project, and wonders why it does not execute properly. Sometimes this is obvious, sometimes not. For the cases when it is not obvious, there could be a special build flag, applies solution-wide, that would emit an *error* if SkipPostSharp is set but PostSharp is required anyway.

Automatic injection of dependencies using existing frameworks.

Automatic implementation of IClonable

Automatic generation of Equals and GetHashCode.

Have you planned to add a quick way to implement a C# singleton for a class ?

Currently only Git and TFS are supported for the feature "Do not require a license to build unedited projects". Add support for SVN.

I was going to try to create an aspect that introduced the ISerializable interface to classes, but there does not appear to be a way to add the constructor that is required of classes that implement this interface. Could this ability please be added?

It would be great to have the ability to filter pointcut selection based on qualities of both Multicast and Method. The ask is that the powerful Multicast filtering is applied first (no need to apply logic in the method) and then the results are passed into the method pointcut.

Hopefully this makes sense. Please let me know if there are any questions, as always!