Is there a way to do reflection pre-compile - at design time?
My intent is to use T4 to spit out custom codes based on classes that implement certain interfaces. I know I can call upon reflection, but I want the T4 script to spit out the additional code before compile, otherwise I will need to compile the code twice, once to generate dlls, twice to let T4 reflect on the previously generated dll and add additional scaffolding.
Is there a way to do reflection at design time?
Is there a better way to do this?
There actually is a way of generating code pre-build based on the CodeModel provided by Visual Studio Automation: The Project Interface provides a Property "CodeModel" that contains a graph of all model artifacts in that project. You might want to traverse it in order to find classes, interfaces, properties, ... based on which you generate your output code.
dandrejw already mentioned the Tangible T4-Editor. It has got a free template gallery. There is a reusable template "tangible Visual Studio Automation Helper" which should be extremely helpful in your case. Using this template you could solve your issue like this:
This is code within a t4 template detecting all classes that implement INotifyPropertyChanged.
Put your output code where the code snippet says "Render your code here".
The only way I know of to do this is to make use of some code parsing capability. I can't think of a way off the top of my head how to do that. I'm sure .NET has some utilities that can do that.
I'm not sure what your situation is, but usually instead of reading code, you have some centralized piece of information, be it an XML file or some UML diagram (class diagram even) that is used to generate code from. It simplifies things a bit and makes it easier to make changes and let code generation spit out the changes. Have a look at the Tangible T4 tools for Visual Studio.
For any future readers not in the mood to try and get the T4 VisualStudioHelper template working, below is a self-contained template which enumerates all the classes in the current project. It is tested in Visual Studio 2013 and was inspired by the code on the T4 Site