signing fails after update of unsigned assembly about signreferences

[vatirim]

Another strange side effect which may be related:
After killing the msbuild process after step 4, SignReferences wants to sign again but this time the ildasm.exe GUI shows up and does not close on its own. The GUI has the assembly open and seems to know the out file name too. Only restarting VS prevents the GUI from showing up. If I use the GUI to save the il file in the temp folder, the rest of the signing works.
I thought, maybe some process is locking the assembly to be signed. So I called idasm.exe with the same parameters as does SignReferences, while the idasm GUI was still up. This second call worked as it should and created the .il. Also running the same C# code (to start idasm) in another test project works. Very strange.
This means, even if one would fix the issue above of the FileLoadException, there might still be this issue which hits afterwards.

[picrap]

Sure, why not.