And if you have SA5 and SA6 side-by-side installed, then you need to restart VisualStudio everytime you want it to use one or the other build task, seems the first one loaded remains loaded for the rest of the app lifetime, independent of project settings.
Yeah, Visual Studio has a limitation where it doesn't detect changes in .targets files in the same way that it does for .csproj files. I've been annoyed by it before.
Having said that, it loads SmartAssembly.exe into the memory of VS when you first use it, so if you've already run a build, the installer should complain that it can't do the install unless you close VS.
Comments
Having said that, it loads SmartAssembly.exe into the memory of VS when you first use it, so if you've already run a build, the installer should complain that it can't do the install unless you close VS.
Developer,
Red Gate .NET Tools