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. PostSharp contains ready-made implementations of the most common patterns and gives you the tools to build au
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.
Tutorials are provided out of the box, the built-in controls for automatically applying various OOB aspects to your code are remarkably helpful and when you're just trying to implement something on your own, their documentation (and the aforementioned tutorials) are remarkably helpful. This is definitely quite a useful tool and highly recommended for any serious development.
Very nice solution providing a faster development approach with cleaner code. Rapid upgrades of PostSharp it self guarantees continues development and reliability. I wish that there were more tools like this.
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.
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.
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.
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.
The issue has been reported in our support forum (http://support.sharpcrafters.com/discussions/problems/2707-c-project-properties-build-and-debug-options-disappear-after-installing-postsharp-4114). We will follow up there.
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.