This code (in a containing class which is re-instantiated for the second
compile) results in a generated executable that is stuck "in use" (can't be
removed etc) until the process itself terminates. I've tried several detours,
none of which help. Any suggestions, or is it a FW bug?

public bool  CompileFile (string filename, string Executable)
 {
  VBCodeProvider codeProvider = new VBCodeProvider();
  ICodeCompiler icc = codeProvider.CreateCompiler();
  string Output = Executable;
  System.CodeDom.Compiler.CompilerParameters parameters = new
CompilerParameters();
  parameters.ReferencedAssemblies.Add ("System.dll");
  parameters.ReferencedAssemblies.Add ("System.Web.dll");
  parameters.ReferencedAssemblies.Add ("System.Management.Dll");
  parameters.ReferencedAssemblies.Add ("System.Windows.Forms.Dll");
  parameters.ReferencedAssemblies.Add ("Microsoft.VisualBasic.Dll");
  parameters.GenerateInMemory = false;
  //Make sure we generate an EXE, not a DLL
  parameters.GenerateExecutable = true;
  parameters.OutputAssembly = Output;
  CompilerResults results = icc.CompileAssemblyFromFile (parameters, filename);
  codeProvider.Dispose();
.....
}