How to debug/break in codedom compiled code.

Question

I have an application which loads up c# source files dynamically and runs them as plugins. When I am running the main application in debug mode, is it possible to debug into the dynamic assembly? Obviously setting breakpoints is problematic, since the source is not part of the original project, but should I be able to step into, or break on exceptions for the code?

Is there a way to get codedom to generate PDBs for this or something?

Here is the code I am using for dynamic compliation.

CSharpCodeProvider codeProvider = new CSharpCodeProvider(new Dictionary<string, string>() { { "CompilerVersion", "v3.5" } });
        //codeProvider.
        ICodeCompiler icc = codeProvider.CreateCompiler();

        System.CodeDom.Compiler.CompilerParameters parameters = new CompilerParameters();
        parameters.GenerateExecutable = false;
        parameters.GenerateInMemory = true;

        parameters.CompilerOptions = string.Format("/lib:\"{0}\"", Application.StartupPath);

        parameters.ReferencedAssemblies.Add("System.dll");
        parameters.ReferencedAssemblies.Add("System.Core.dll");


        CompilerResults results = icc.CompileAssemblyFromSource(parameters, Source);
  DLL.CreateInstance(t.FullName, false, System.Reflection.BindingFlags.Default, null, new object[] { engine }, null, null) ;

Answer 1

Try the following options:

parameters.GenerateInMemory = false; //default
parameters.TempFiles = new TempFileCollection(Environment.GetEnvironmentVariable("TEMP"), true);
parameters.IncludeDebugInformation = true;

I am not sure if this works OK in your case, but if it does, you can surround this parameters with conditional compilation directive, so that it dumps the generated assembly only in debug mode.

Answer 2

The answer by @bbmud is correct, though misses one bug fix. The CSharpCodeGenerator (the class in .NET the compiles C# code to IL) is programmed to remove pdb files immediately after they are create (I copy the code), UNLESS on adds "/debug:pdbonly" to the CompilerOptions string. However, if you do that, the IncludeDebugInformation is ignored and the compiler generates optimised code which is hard to debug. To avoid this you must explicitly tell the Code Generator to keep all files.

Here is the complete recipe:

parameters.GenerateInMemory = false; //default
parameters.TempFiles = new TempFileCollection(Environment.GetEnvironmentVariable("TEMP"), true);
parameters.IncludeDebugInformation = true;
parameters.TempFiles.KeepFiles = true

Here is the culprit part of the code of CSharpCodeGenerator:

  string fileExtension = "pdb";
    if ((options.CompilerOptions != null) && (CultureInfo.InvariantCulture.CompareInfo.IndexOf(options.CompilerOptions, "/debug:pdbonly", CompareOptions.IgnoreCase) != -1))
    {
        results.TempFiles.AddExtension(fileExtension, true);
    }
    else
    {
        results.TempFiles.AddExtension(fileExtension);
    }

The TempFiles.AddExtension(fileExtions,true) tells the compile to keep the pdb files. results.TempFiles.AddExtension(fileExtension); tells it to treat pdb as all temporary files which by default means delete them.