Closed jeffmcardle closed 11 years ago
@jeffmcardle just guessing here as I'm not familiar with the code, but maybe the problem is that this T4MVC.tt.settings.xml
file didn't exist when AutoT4MVC was first written, so it needed to be modified to account for it.
@bennor any thoughts?
Maybe this is a T4MVC issue and not AutoT4MVC specific. Does it repro when you manually run the custom tool?
To run the template, all AutoT4MVC does is open and save the T4MVC.tt file(s) (triggering a rerun). The other files that T4MVC uses (or generates) shouldn't matter and the result should be the same as if you run it manually.
The only thing the code does with T4MVC.tt.settings.xml
is monitor it for changes (so if you change your settings, a rebuild is triggered).
I suspect that some part of the template itself is saving the settings file (perhaps by accident).
I will check tonight to make sure that it's not incorrectly detecting the settings file as a template (and therefore opening and saving it), but looking at the code it's doing a direct StringComparer.OrdinalIgnoreCase.Equals()
comparison on the project item name, so it shouldn't be.
Yes, see my latest comment on http://t4mvc.codeplex.com/discussions/403390. It's not your issue :)
@jeffmcardle a fix is available is T4MVC. Please see codeplex thread for details.
Thanks guys. Checking it out now.
This causes a build error. Is there any way to make it automatically check this file out from source control?