Tag Archives: PostSharp
Recently at a conference I was given the opportunity to talk about Aspect Orientated programming with PostSharp. In my demo I showed off the difference between creating an INotifyPropertyChanged class manually, using boilerplate code generated by Resharper, and using smart … Continue reading
This year was my second year presenting at the South Florida Code Camp. I am once again amazed at the amount of attendees, number of sessions, and of course the great folks you get to meet and learn from.
This coming weekend (Feb 9th) I will be giving two presentations.
On the 26th the great folks at SharpCrafters announced the much anticipated PostSharp 3 CTP (Community Technical Preview). There are many changes in this CTP so lets review some of them. For anyone new let me start by a quick … Continue reading
The question came up today ‘How can I store my aspects in a single project in my solution and allow them to be usable across my application” Luckily for us PostSharp follows DRY and SRP so this is fairly straight … Continue reading
To continue on from Part 2. For this article we will talk about one of the aspects I utilize the most OnExceptionAspect Note: This may be the last generic post, I am working on a new blog series will show … Continue reading
To Continue on from Part 1 lets dive a little deeper into Aspect Oriented Programming utilizing a framework called PostSharp Setup Windows 7 X64 Visual Studio 2010 (if I get a large enough feedback I will switch this series to … Continue reading
Note: This so far is working on any targeted project that Visual Studio 11 except .NET 4.5. If something specific is not working on say .net 4 or 3.5 please let me know and I will update this post. Just … Continue reading
My big week has finally ended.. As always when one chapter closes another opens along with back to writing post. To recap I was given a great opportunity by SharpCrafters to present on: Introduction to Aspect Oriented programming using PostSharp.
For those new to SRP, it stands for Single responsibility principle. Here is a snippet from Wikipedia on the meaning. In object-oriented programming, the single responsibility principle states that every object should have a single responsibility, and that responsibility should … Continue reading