So there are two scenarios for managing an msbuild task assembly.
1 Stored under the solution so it can be checked in to source control
2 Stored somewhere globally
In case 1 placing MyMsBuildTask.dll in a temp dir does not update the current instance of VS to the new file. Nor does it overwrite the "checked-in" file so it can be picked up by source control and checked in. I could modify the csprojto point to the temp
dir, but this would effectively break the source control approach.
In case 2 we have the same "current instance will not update" and also have other issues since MyMsBuildTask.dll may be locked by multiple instances of VS
So this is the current hack I have had to use this approach http://code.google.com/p/notifypropertyweaver/wiki/Nuget
The problem is it effectively kills the users ability to update the package.