Add support for extension based config item #97
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is to address feature request I've created #96.
Behavior
Once extension is added to config file then all the files with that extension are compiled without need for adding them to the config.
Right click on the file with a configured extension will not have option to be removed from the compiler config.
Recompile all will also compile all files matching the extension.
Running the compilation from Task Explorer will compile all files matching the extension.
To avoid performance impact, folder scan for files matching extension is cached.
New files, added through visual studio, that match the extension will also be compiled.
Known Issue
If files are added outside visual studio while the project is open, we need to run recompile all for the file to be included in compilation.
With these changes the extension supports config file like this.
And task explorer shows this