Currently, calling a decorated method concurrently invokes the method twice. For more information and a workaround, see http://support.sharpcrafters.com/discussions/problems/4347-cache-aspect-concurrency

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.

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.

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 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.

As a developer I do expect property changes to be raised even when i depend on external static fields.
This issue has been pointed out in the following thread:
http://support.sharpcrafters.com/discussions/questions/1565-notifypropertychanged-and-static-property

I lost a lot of time trying to understand what i was doing wrong before contacting the support because it felt like it should just work to me.

Honestly, i don't understand exactly what the problem is but, i have been told it's a design choice and I have been provided with a working workaround.

Couldn't this workaround be automated by postsharp?

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?

For example, allow the user to implement IAdviceProvider and return an AdviceInstance for each property to be introduced. Each AdviceInstance will specify the name and type of the property, and getter and setter methods to be invoked. The introduced properties are not required to be defined in the corresponding user aspect type.

This feature will be available as context menu when you right click on project."Make it better" feature : when this is clicked,
a background worker will now scan that entire project and
thereby "highlights" in some side-bar or alike so as to suggest, which areas of that project code can be made better using PostSharp's existing set of specific features