Skip to content

Releases: bennor/AutoT4MVC

1.5.3: Support for Visual Studio 2017

21 Mar 20:32
Compare
Choose a tag to compare

No functional changes again, but VS 2017 is now supported.

Note: May require installing .NET 4.6 when using with older versions of VS.

Thanks to @rjregenold for implementing this. ✨

1.5.2: Support for Visual Studio 2015

20 Nov 12:06
Compare
Choose a tag to compare

No functional changes, but AutoT4MVC will now run in Visual Studio 2015 Preview. It should "just work" when RTM hits too.

:bowtie:

1.5.1: Updated documentation links in VSIX

12 Apr 02:01
Compare
Choose a tag to compare

Updated the following documentation links in the installer:

There are no functional changes to the extension in this version, so you won't miss anything if you skip it.

1.5.0: Smarter change monitoring

10 Apr 10:14
Compare
Choose a tag to compare

Now uses settings from T4MVCSettings.xml to determine which files & folders to monitor for changes, thanks to Gary Sharp.

This means that whichever folders have been set up for controllers, views and static files in the settings file for a project will be the ones monitored for changes.

Anyone still using the deprecated T4MVC.tt.settings.t4 file will now only have the standard MVC folders monitored (i.e. Controllers, Views, Scripts and Content).

1.4.0: Options dialog

11 Apr 21:53
Compare
Choose a tag to compare

Added an options dialog with these options:

  • Run on save (which rebuilds the template when MVC files are created/updated/deleted, e.g. controllers, views, content files)
  • Run on build (which rebuilds the template when the project or solution is built)

The options dialog can be accessed quickly via the Solution Explorer context menu of any T4MVC.tt file:

image

1.3.0: Visual Studio 2013 support

11 Apr 23:40
Compare
Choose a tag to compare

Added support for Visual Studio 2013. (2012 is still supported.)

1.2.0: Throttling & "Run Custom Tool"

11 Apr 23:39
Compare
Choose a tag to compare
  • Added throttling for multiple events within a short space of time (to avoid reprocessing template when adding/removing a whole directory of files, etc).
  • Now uses the Run Custom Tool command to avoid an unnecessary checkout of the template file.

1.1.2: Additional "on save" trigger for new T4MVC settings file

11 Apr 23:36
Compare
Choose a tag to compare

Added triggering on save of T4MVC.tt.settings.xml.

1.1.1: Additional "on save" triggers

11 Apr 23:35
Compare
Choose a tag to compare

Added additional template rebuild triggers:

  • On add/remove/rename of a file in any of the following folders (case-insensitive): Assets, CSS, Images, JS or Styles.
  • On save of T4MVC.tt.settings.t4.

1.1.0: "On save" triggers

11 Apr 23:33
Compare
Choose a tag to compare

T4MVC templates are now run under the following conditions:

  • a project or solution containing the template is built
  • a file in a Controllers folder (case-insensitive) is saved (in the same project)
  • a file is added/removed/renamed in any of the following folders (case-insensitive) Controllers, Views, Scripts or Content (in the same project)