35 | AutoRunCustomTool
36 | 37 |Download from Visual Studio Gallery
38 | 39 |A Visual Studio extension that automatically runs the custom tool on another file when a file is modified
40 | 41 |OK, I realize that this description is perhaps not very clear, so let's take an example. Let's assume (well, it's not really an assumption; it's actually the scenario that caused me to create this tool) that in your project, you can't (or don't want to) use the default custom tool for resx resource files. Instead, you use a T4 template to generate the code associated with the resx file. So you have 3 files :
42 | 43 |-
44 |
- 45 | Strings.resx, that contains the actual string resources 46 |
-
47 | Strings.tt, a T4 templates that generates code to access the resources from Strings.resx
48 |
49 |
-
50 |
- 51 | Strings.cs, a C# source file that is generated by Strings.tt based on the content of Strings.resx 52 | 53 |
55 |
The problem with this setup is that Visual Studio doesn't know that a change to Strings.resx should cause a regeneration of Strings.cs, so when you just added a resource to the resx file, it's not immediately available to your code, and doesn't appear in Intellisense. You have to right-click Strings.tt and select "Run custom tool" so that the template is run again. This is very annoying...
56 | 57 |This VS extension solves the problem very simply: when it detects a change to the "trigger" file (Strings.resx), it reruns the custom tool for the "target" file (Strings.tt).
58 | 59 |Note that this was just an example; the trigger file doesn't have to be a resx file, and the "target" file doesn't have to be a T4 template. Both can be anything you want, as long as the target has a custom tool defined.
60 | 61 |62 | How to use
63 | 64 |After you install the extension, you should see a new Run custom tool on property on each project item. Just edit this property to add the name(s) of the target file(s). That's it!
65 | 66 |Here's a screenshot that shows how it works:
67 | 68 |
Note to users of previous versions: in previous versions, you had to set the Custom Tool property for the trigger file to "AutoRunCustomTool", and set the Custom tool namespace to the name of the target file. This sometimes caused a warning in Visual Studio : "Cannot find custom tool 'AutoRunCustomTool' on this system.". I changed the way the extension works so that it doesn't use the Custom Tool property anymore. To ensure compatibility with existing projects, the Custom Tool approach is still supported, but not recommended.
71 |