An open source .NET compile-time code amender.
Switch branches/tags
Nothing to show
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
Afterthought.Amender Update to support Roslyn metadata Mar 13, 2017
Afterthought.UnitTest.Target Updated assembly amending logic to correctly mark instruction points … Nov 26, 2013
Afterthought.UnitTest Updated amending process for methods to support context-based before … Nov 11, 2013
Examples Updated amending process to alter how After delegates are invoked to … Nov 21, 2013
Microsoft.CCI Updating to latest version of Microsoft.Cci libraries from CodePlex p… Sep 9, 2011
.gitignore Update .gitignore to ignore unit test results. Apr 12, 2011
Afterthought.1.0.6.nupkg Updating NuGet version to 1.0.6 to address dll reference issue when a… May 3, 2011
Afterthought.1.0.8.nupkg Adding entity framework example (just core without tests), fixed over… May 11, 2011
Afterthought.png Removed dependency on Parameter<> class to allow amended assemblies t… Apr 25, 2011
Afterthought.sln Afterthought changes to get team build working and resolve conflict o… Aug 4, 2015
Afterthought_Icon.png Adding NuGet icon Apr 29, 2011
NuGet (pack with source).bat Updating NuGet version to 1.0.6 to address dll reference issue when a… May 3, 2011
NuGet (pack without source).bat Edited via GitHub Apr 8, 2011
vc3os-sm.png Adding NuGet and open source logo Apr 8, 2011

Afterthought allows developers to post-process .NET assemblies to add code that either cannot be added to the original source or is not convenient/efficient to do so. Examples include:

  1. Tweaking a compiled assembly for which you do not have the source code be must support/modify
  2. Adding instrumentation logic to an assembly for test purposes, which will not always be part of the release version
  3. Implementing tedious interfaces or patterns that get in the way of the simplicity of your coding efforts when directly implemented.

We developed Afterthought specifically based on our experience with PostSharp. While we enjoyed PostSharp and the advantages it provides, this product has two downsides:

  1. The developer experience is a bit complicated, introducing new concepts like aspects and generally requiring you to understand how PostSharp works internally to make it work for you. It required you to frequently cast objects to known types instead of writing fluent strongly-typed intuitive code. Lastly, the emitted code to do something very simple is very complex--dozens of lines of code just to call one line of your own code.

  2. PostSharp is no longer free. We have been developing open-source libraries for the past couple of years, and as we prepared to release them publically, we realized that some dependencies on PostSharp made our own open source efforts less appealing. The introduction of Afterthought eliminates this issue by providing a completely free option.

So, what does Afterthought do? Quite simply, it allows you to:

  1. Create type amendments by subclassing Amendment<,> to describe what changes you want to make
  2. Add attributes to your types indicating which types to amend and what amendments to apply
  3. Amend properties by either adding new properties or modifying the logic of existing properties
  4. Amend methods by either adding new methods or modifying the logic of existing methods
  5. Amend constructors by either adding new constructors or modifying the logic of existing constructors
  6. Implement interfaces directly on a type leveraging existing properties/methods, adding new properties/methods, and allowing Afterthought to automatically implement everything else
  7. Configure your project to call Afterthought as a post-build step to apply the changes