I'm using PostSharp since version 1. First, it is the only one which can do AOP very easy and is flexible enough for the use in professional and big projects. I have used it in 3 big projects, without any effort. If you need AOP in an extended way, you need PostSharp!
I think it is the next best thing ever happened to C# after LINQ.
Years after years of coding with the same language with using same things all over again and again slowly takes away all the joy and the feel of you actually creating something. Then I found about PostSharp at a point where I was considering to stop using C# all together and it simply amazed me as I realized how better and simpler I could have coded my years of effort if it existed from the beginning.
I even think Microsoft should acquire them and make it a fundamental part of the .NET framework.
Best extension for AOP! Reduces code re-wirte and helps us focus on much important to-do code ! Adds value by increasing maintainability..Increases separation of concerns ! The increased presence of transaction can be of great hep in certain scenarios..All goodies of AOP follow along with a great, mature product !
This is a superb tool, worth it for the automatic implementation of INotifyPropertyChanged alone. If you've ever developed for MVVM under WPF, you won't believe how easy this makes it. You just decorate your class with an attribute, and INotifyPropertyChanged is magically implemented - it even takes care of dependencies between properties.
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.
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 "postsharp.xxx.vsix" 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.
In normal times you can use the extension in commercial projects.
However, the current version is a pre-release and is governed by our Evaluation License, which does not allow for use in production. Please use our current stable release 2.1 (http://www.sharpcrafters.com/download) for a version that can be use commercially today.