VSIP Partner Free

PostSharp is the #1 pattern-aware extension to C# and VB. It allows developers to eradicate boilerplate by offloading repeating work from humans to machines. Includes some the most common patterns and gives you the tools to build your own.

(100) Review
Visual Studio
2015, 2013, 2012
Download (203,528)
E-mail Twitter Digg Facebook
Add to favorites
Reviews (100)
Q and A (12)
Sign in to write a review
Sort by:

by DelegateVoid | January 27 2016

To me PostSharp is all about removing repetitive tasks and validation outside of the main business logic, keeping the code clean and maintainable. It's probably the first thing I add to every new project.

by SamSeriouss | January 21 2016

As a student learning C# this makes my life so much easier and avoids me making many mistakes. This way I can focus more on the actual endproduct, not having to lose time Writing common patterns.

by Evert Wiesenekker | January 13 2016

To my opinion if you are doing serious software developement this tool is '[Required]'. It eliminates a lot of boilerplate code regarding logging and validity checks.

by NaxAlpha | January 08 2016

Writing beautiful code and managing large projects is must for indie developers to make better project and it becomes very easy when using PostSharp, which allows one to focus on business logic instead of code complications.

PostSharp allows me to have my requirements fulfilled.

by Kevin Poon | December 25 2015

I love this tool! It has been reducing boiler plate code a lot and makes my live as developer much easier.

by Jonyadamit | December 23 2015

The whole concept of AOP through IL weaving is amazing.
This allows you to write code that is both performant and maintainable!

PostSharp allows you to do that, with a very mature framework that is constantly being maintained and improved.

I'm a fan.

by AnthonyS89 | December 07 2015

Very happy with their BizSpark program.

by Jacek Łapiński | December 01 2015

It is really great tool. My code is much cleaner and I can work much faster.

by Abdul-Rahman Ahmad | November 23 2015

When I used PostSharp first time,I was looked to it as secondary tool,
But now it is an essential part of my projects, because PostSharp lets me focus on business logic, while it is interested in other things like pattern model or logging or any cross tasks.

Thank a lot for PostSharp team.

by ALeblond | November 22 2015

PostSharp is a great tool! It works very well! AOP makes development so much faster with less boilerplate code.

by Mike James Miles | October 07 2015

The key developers tool for every day use - 10 out of 10

by Richard.Urwin | September 11 2015

Incredibly useful, specifically OnMethodBoundaryAspect.OnException(...) for catching exceptions and sending to reporting infrastructure.

by Andrew Stanton | August 03 2015

P# is very useful. I do wish they would publish updates less frequently, it feels like every time I open up VS, there is another update needed.

by Bruno Sonnino | July 13 2015

PostSharp is a great tool for implementing AOP. With it, it's easy to add boilerplate code and implement repetitive code without messing with your main code

by Ricardo Peres | July 10 2015

The de facto standard for post-build AOP in the .NET world!

by RVHelden | July 08 2015

Postsharp works really well, I really like the logging and threading features that it provides.
Its easy to apply Aspects to the code and to create aspects yourself if the provided aspects don't fit your situation.

by Jaffi | July 08 2015

Simple, strong and reduce a lot of coding... A tool that every developer should have in his tool box.

by Ted.Huang.TKU | June 29 2015

It felt amazing!

by Kjetil Tonstad | June 24 2015

Great tool!

by Alejandro Pi | June 22 2015

1 - 20 of 100 Items   
Sign in to start a discussion

  • The Signature of PostSharp-4.2.18.exe is corrupt or invalid
    2 Posts | Last post February 02, 2016
    • When trying to download the latest version of PostSharp, IE throws fails signature validation. I am attempting to download to install tools for VS2015. 
    • Thank you for reporting the issue. We are working on it. It seems to be related to the deprecation of SHA1 in Authenticode.
  • Disabling nug window PostSharp Configuration on try to compile a project inside VS
    4 Posts | Last post December 22, 2015
    • First of all I should say I hate your product (P#). I use it just because other my team mates prefer not to write contracts for methods but use your automagic to imitate some of them. We had so many troblems with your magic!
      Now we did upgraded our environment from mix of VS2010 and VS2013 to pure VS2015. During this process we upgraded P# from 2.2something to 4.1.14. I don't know why it isn't the last verision, hope it doesn't mean a lot. We used to put version 2 into TFS but version 4 requires to install it using NuGet and seams like you don't support old scenario. It is the first hate-point. But anyway I've put P# into TFS and unistalled it from my VS. We really don't need all of your fancy features, just some aspects to control not null parameters and things like that. I can build the product from command line. It's ok but had to remove so many junk you add when install P# using NuGet!!! It is the second hate-point 'cause I should remove this junk from more than 100 projects.
      After I've removed this very extension from my VS I cannot build any project from inside VS! This THE MAIN hate-point! Every time I try to do it, I have a nug window "PostSharp Configuration" with request to Install PostSharp Tools for Visual Studio!
      How I can avoid use your f... extension for VS and still use your odd job P#?
    • Hi Mike,
      I'm sorry to hear your disappointment with the new version. I would like to thank you for sharing your negative experience. It is very useful. Positive feedback makes us feel good, but negative feedback makes us progress. The latter is more important.
      You pointed very important points. Other users have mentioned the same frustrations and we already started working on it. We decided to address the following points in PostSharp 4.3:
      1. There will be an alternative to using NuGet. The old good "zip" distribution will be back.
      2. The VS extension will no longer be required. However it will be highly recommended if you want to have a decent debugging experience.
      3. We will have a proper uninstaller.
      4. We will not require a license to compile project that have been just freshly checked out from source control and not modified.
      To answer your question specifically, you can avoid  using the extension by defining the following environment variable or MSBuild property:
      As a last point, please note that PostSharp is not for everybody and for every project. If your colleagues selected PostSharp only for code contracts, it is possible that the code savings may not pay off the friction. The more patterns you automate with PostSharp, the more it pays off. We can neither validate neither invalidate the design decisions that your team did. PostSharp is a sharp tool, and needs to be used with care.
      I hope this helps.
    • Thank you Gael for your positive answer on my negative and emotionfull feedback! I really don't like any "magic" in code but I should use it in our code. I prefer to be explicit in my code.
      Anyway thank you for your replay. I'll check it out.
    • I've created environment variable PostSharpSkipVsxCheck=True, reloaded VS and rebuilt a project. That works! No nug window anymore!
  • Silent installation for post sharp tools
    3 Posts | Last post December 20, 2015
    • Hi.
      I want be able to silent install post sharp tools for visual studio,
      Using the post sharp trial version.
      I tried to use the .vsix file,
      but considering that I don't have a license it is problematic.
      Is there a way to do that?
    • Silent installation is currently unsupported. We will work on this in PostSharp 4.3.
    • Hi Gael.
      There is a real need for it.
      I am looking forward to this version/feature to be ready. 
  • Alex G
    2 Posts | Last post November 26, 2015
    • Hi guys, I tried to install PostSharp for VS 2015 under Windows 10 and I've got unexpected error, can you help me with that?:
      ---> PostSharp.Sdk.UserException: Could not start VsixInstaller.exe: The VSIX installer process failed with exit code -532462766. ---> PostSharp.Sdk.UserException: The VSIX installer process failed with exit code -532462766.
         в PostSharp.HQ.Vsx.VsxProcess.InstallVsxTask.ExecuteVsix(String vsixPath, Boolean elevated) в c:\src\PostSharp-4.1\UserInterface\PostSharp.HQ\Vsx\VsxProcess.cs:строка 428
         --- End of inner exception stack trace ---
         в PostSharp.HQ.Vsx.VsxProcess.InstallVsxTask.ExecuteVsix(String vsixPath, Boolean elevated) в c:\src\PostSharp-4.1\UserInterface\PostSharp.HQ\Vsx\VsxProcess.cs:строка 433
         в PostSharp.HQ.Vsx.VsxProcess.InstallVsxTask.Execute() в c:\src\PostSharp-4.1\UserInterface\PostSharp.HQ\Vsx\VsxProcess.cs:строка 401
         в System.Threading.Tasks.Task.Execute()
    • -532462766 is general exit code for unhandled exception. This usually happens when the installer is executed with insufficient rights. We are going to address these kind of issues soon. In the mean time please, could you try to run the installer as administrator? If it doesn't help, please could you report this issue to our forum ( and attach a VSIXInstaller_*.log file that is created during installation in %temp% folder?
  • silent install
    6 Posts | Last post August 21, 2015
    • Hi, I need to deploy this extension on a farm of machine. Is there is a silent or unattended installation option?
      I tried /q but got a pop up command prompt instead.
    • If you're talking of a farm of build servers, then PostSharp does not need to be installed at all because it is deployed through NuGet.
      If you need to deploy the VS tooling to many desktop stations, the best is to ask all developers to install it manually on their machine. If you're a commercial customer please contact our support and we may be able to help automate the deployment, but there is no easy option.
    • If the official answer is that I can no longer have an unattended install option to my development environment, then I guess I'll have to look at one of the other Aspect-Oriented frameworks out there... Please don't let the answer be, "Install it manually..."
    • Could you please explain your deployment scenario? We generally don't get requests for unattended installation even from commercial teams of hundreds of users, so I would like to understand why it is so important to you.
      Thank you.
    • I work in an environment of about 60 developers where we try to automate every install we can... This allows us to pave a machine and then reinstall the complete development environment quickly and also ensures that the version of the Visual Studio extension stays the same across the environment. In the past, I've used the "vsixinstaller /q /a /i "" to install the extension into Visual Studio. We still use NuGet to handle the actual DLLs which is how the build servers get PostSharp and where the version of the PostSharp DLL is also project specific. The download link above now points to an EXE file instead of a VSIX file and the EXE appears to not have any way to script the install of the extension. My organization hasn't moved to this version yet and the older NuGet packages that we are using will install the extension relevant to the version of PostSharp used in the project so, for now, we’ll stick to that deployment method.
    • Sorry for late answer, I did not notice your reply.
      You can download the exe file from VS Gallery and unpack it with 7-zip. You will find two VSIX files inside, one for VS 2012 and one for VS 2015. From there you can use VSIXInstaller.
      I hope this helps.
  • Cannot installed on VS 2015 Enterprise
    2 Posts | Last post August 20, 2015
    • I can't install the PostSharp's extension on VS 2015 Enterprise, when I trying to install it, it says "Install 'PostSharp Tools for Visual Studio 2012-2013', at the end its installed on VS 2013 that I also have installed but no in VS 2015. I'm running on Windows 10 x64 Enterprise.
    • I've notice that it was previously installed, but for some reason I was enable but no available. I just uninstalled and re-installed and everything is working pretty fine.
  • Extension version VS DLL version
    2 Posts | Last post August 13, 2015
    • How important is it that the extension version matches the referenced dll version?
    • Not very important. There is no need to keep exact match between dll and the extension. If the extension is much older than the dll, then the extension could add some code (e.g. via code actions) that is not compatible with the new dll.
  • Version 4.1.14 disables build tab in C# project
    3 Posts | Last post June 24, 2015
    • Version 4.1.14 disables the "build" tab ( in C# projects. Can we get a ix for it?
    • The issue has been reported in our support forum ( We will follow up there.
    • ok, I've updated to 4.1.15 and the issue is fixed.
  • ETW support for logging
    6 Posts | Last post June 06, 2015
    • Do you have any plans to also support ETW ( as logging option in PostSharp (
    • There is no plan to implement support for ETW (we didn't exclude it) but we do plan to make it possible to write custom back-ends much more easily than before. This work is planned for the winter.
    • ok, thanks.
    • any progress about this?
    • This is planned for PostSharp 4.3 with first releases in late String 2015.
    • ok, thanks for the information.
  • Enterprise Library Version
    2 Posts | Last post March 20, 2015
    • What versions of Enterprise library can be used with PostSharp's logging features? Only > 5.0?
    • Yes, we have a dependency to EnterpriseLibrary.Logging 5.0.505.1.
1 - 10 of 12 Items