Thomas Levesque • 11/14/2013

Running a custom tool automatically when a file is modified

Read Original

This article explains the problem of Visual Studio's custom tools (single-file generators) not automatically running when a template's dependent input files change. It introduces the author's solution: a free, open-source Visual Studio extension called AutoRunCustomTool. The extension adds a property to project items to specify which files should trigger a custom tool run, streamlining workflows for T4 templates and similar scenarios.

0 comments
#Visual Studio #Custom Tools #File Monitoring
Running a custom tool automatically when a file is modified

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
React, useEffect, and Stale Closures: How to Avoid Them with Dependencies and useRef
Jivbcoop • 4 votes
2
Better react-hook-form Smart Form Components
Maarten Hus • 2 votes
3
AGI, ASI, A*I – Do we have all we need to get there?
John D. Cook • 1 votes
4
Quoting Thariq Shihipar
Simon Willison • 1 votes
5
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft • 1 votes
6
Using Browser Apis In React Practical Guide
Jivbcoop • 1 votes