Can't delete a compiled file - "file in use"

I'm running the code below that compiles and runs a dll. It works great - except when the program loops back around it can't delete the existing dll because "file is in use"
Once the dll below is created and run, how can i released it so i can then delete it?
Try
            If m_Code.Trim <> "" Then
                If m_Namespace.Trim <> "" Then
                    If m_ClassName.Trim <> "" Then
 
                        Try
                            If File.Exists(m_AppPath & "\" & m_Namespace & ".dll") Then File.Delete(m_AppPath & "\" & m_Namespace & ".dll")
                            If File.Exists("c:\windows\system32\" & m_Namespace & ".dll") Then File.Delete("c:\windows\system32\" & m_Namespace & ".dll")
                        Catch
                        End Try
 
                        Dim VBP As New VBCodeProvider()
                        Dim CVB As System.CodeDom.Compiler.ICodeCompiler
                        CVB = VBP.CreateCompiler
                        Dim PM As New System.CodeDom.Compiler.CompilerParameters()
                        PM.GenerateInMemory = False
                        PM.OutputAssembly = m_Namespace & ".dll"
                        PM.MainClass = m_ClassName
                        PM.IncludeDebugInformation = True
 
                        'Add assemblies
                        Dim ASM As System.Reflection.Assembly
                        For Each ASM In AppDomain.CurrentDomain.GetAssemblies()
                            PM.ReferencedAssemblies.Add(ASM.Location)
                        Next
                        PM.ReferencedAssemblies.Add(m_AppPath & "\ActiveReports.dll")
                        PM.ReferencedAssemblies.Add(m_AppPath & "\ActiveReports.XlsExport.dll")
                        PM.ReferencedAssemblies.Add(m_AppPath & "\ActiveReports.PdfExport.dll")
                        PM.ReferencedAssemblies.Add(m_AppPath & "\ActiveReports.Viewer.dll")
                        PM.ReferencedAssemblies.Add(m_AppPath & "\interp.business.dll")
 
                        'here we do the deed
                        Dim Results As System.CodeDom.Compiler.CompilerResults
                        Results = CVB.CompileAssemblyFromSource(PM, m_Code)
 
                        'this is just to list out all the errors if any
                        Dim Err As System.CodeDom.Compiler.CompilerError
                        For Each err In Results.Errors
                            m_Results &= "Number " & err.ErrorNumber & " Text " & err.ErrorText & " Line " & err.Line & VbCrLf
                        Next
 
                        Dim RunObj As New Object()
                        Dim vArgs() As Object
                        RunObj = Results.CompiledAssembly.CreateInstance(m_Namespace & "." & m_ClassName, False, Reflection.BindingFlags.CreateInstance, Nothing, vArgs, Nothing, Nothing)
                        If RunObj Is Nothing Then
                            m_Results &= "Unable to run dll - failed." & VbCrLf
                        End If
 
                    Else
                        m_Results &= "No class name found." & VbCrLf
                    End If
                Else
                    m_Results &= "No namespace found." & VbCrLf
                End If
            Else
                m_Results &= "No code found." & VbCrLf
            End If
 
            If Len(m_Results) = 0 Then m_Results = "OK"
        Catch err As Exception
            m_Results &= "ERROR: " & err.Message & " " & err.StackTrace & VbCrLf
        End Try

Open in new window

LVL 1
LosBearAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

melmersCommented:
You can only unload an assembly if it is in another appdomain.
So you must create an appdomain which loads the compiled assembly and when it should unload you must unload the whole appdomain.

Here is an MSDN Magazine Article about it.
http://msdn.microsoft.com/en-us/magazine/cc163476.aspx
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
LosBearAuthor Commented:
Thanks
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic.NET

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.