ICodeCompiler Leaking File Handles in 1.1 FW?

[Matt Gertz]

Phil,
Thanks for the notification on this. I'm going to do some investigation
on this today & try debugging through the problem, and I'll get back to you
either this afternoon or tomorrow morning. (My response will be posted in
languages\vb, since this is likely to be a VB issue -- I'll drop a copy of
this post over there.)

Thanks,
--Matt Gertz--*
VB Compiler Dev Lead

--------------------

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();
.....
}
--
Phil Wilson [MVP Windows Installer]
----

[Matt Gertz]

Phil,
We are still investigating this. One of our testers has a question on
this:

From Alexandre Moura:
I'm doing some investigation on behalf of Matt - I've been trying to repro
this, but having some problems - if I just attempt to compile a file twice,
it seems to be able to do it - also removing or altering the generated .exe
between two compilations in the same process seems to work fine - are you
actually running the generated .exe and attempting to recompile before it
terminates executing?

--------------------

X-Tomcat-ID: 621056989
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
From: ma****@online.microsoft.com (Matt Gertz)
Organization: Microsoft
Date: Thu, 04 Dec 2003 18:33:46 GMT
Subject: ICodeCompiler Leaking File Handles in 1.1 FW?
X-Tomcat-NG: microsoft.public.dotnet.languages.vb
Message-ID: <KC**************@cpmsftngxa07.phx.gbl>
Newsgroups: microsoft.public.dotnet.languages.vb
Lines: 43
Path: cpmsftngxa07.phx.gbl
Xref: cpmsftngxa07.phx.gbl microsoft.public.dotnet.languages.vb:161397
NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122

Phil,
Thanks for the notification on this. I'm going to do some investigation
on this today & try debugging through the problem, and I'll get back to youeither this afternoon or tomorrow morning. (My response will be posted in
languages\vb, since this is likely to be a VB issue -- I'll drop a copy of
this post over there.)

Thanks,
--Matt Gertz--*
VB Compiler Dev Lead

--------------------

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 beremoved 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();
.....
}
--
Phil Wilson [MVP Windows Installer]
----