Added the possibility to chose when to run T4 templates (before build, after build, not at all)

[CosminLazar]

Hi, In my case I need to run the T4 templates after the build finishes, therefore I implemented it.

Except the actual functionality, there are also some changes in the coding style, if they don't appeal to you, I wont mind if you don't take them in :)

Here's the list of changes implemented here:

• Moved all the methods that deal with finding the template files and running them into extension methods, so that the AutoT4Package.cs file is more concise and easy to parse for a newcomer;
• [important] In AutoT4ProjectItemSettings the RunOnBuild is now of type BuildEvent, so that users can chose when they want to run the templates. However, the code does not migrate the previous value (this means that current users updating the extension will lose their previous setting);
• In ProjectItemSettings I wrapped the conversion in a try/catch block;

Please let me know if you intend to accept this.

Have a great day! Cosmin

[CosminLazar]

Added another commit that migrates the previous RunOnBuild setting.

Since the ProjectItemSettings class is so beautifully generic, I implemented the migration as a coercion in the AutoT4ProjectItemSettings. Let me know of your thoughts.

[CosminLazar]

when it comes to the display name of the enum, I initially tried to get it to work but gave up on it :p Will try to check it out again during the weekend and get back at you if I find something.

[bennor]

Cool. I'm at work now so I'll have a look at this tomorrow (Saturday here).

[CosminLazar]

Spent a bit more time looking to see if the BuildEvent enum values can be exposed with a nice display name in the property page, but I don't think it is supported (you will probably have to convert the RunOnBuild property to a string and handle the display name conversion yourself). Anyway, the "raw" enum values are straightforward and self explanatory. Don't think it pays off to put any more work into this.

[CosminLazar]

Super! Can you also push an update of the extension to the Visual Studio Gallery?