Yeah, pain isn't it. Visual Studio holds lock on MSBuild tasks as well.
On Fri, May 11, 2012 at 1:43 AM, Morten Lemvigh
morten.lemv...@novasoftware.se wrote:
When building a setup project using Votive in Visual Studio, a handle is
kept on any extension dlls even after the build has completed.
On 13-05-2012 23:42, Rob Mensching wrote:
Yeah, pain isn't it. Visual Studio holds lock on MSBuild tasks as well.
!Truly! Have you any experience executing the extension in a new
separate AppDomain and thereby being able to unload it again? I started
out but ended up in a dark alley of missing
When building a setup project using Votive in Visual Studio, a handle is
kept on any extension dlls even after the build has completed. This
poses two problems to me:
1. Developing extensions is a slow process, because Visual Studio has
to be restarted every time I have to make a change to
3 matches
Mail list logo