Recompile C# while running, without AppDomains

Let’s say that I have two C# applications - `game.exe` (XNA, needs to support Xbox 360) and `editor.exe` (XNA hosted in WinForms) - they both share an `engine.dll` assembly that does the vast majority of the work. Now let’s say that I want to add some kind of C#-based scripting (it’s not quite "scripting" but I’ll call it that). Each level gets its own class inherited from a base class (we’ll call it `LevelController`). These are the important constraints for these scripts: They need to be real, compiled C# code They should require minimal manual "glue" work, if any They must run in the same AppDomain as everything else For the game - this is pretty straight forward: All the script classes can be compiled into an assembly (say, `levels.dll`) and the individual classes can be instanced using reflection as needed. The editor is much harder. The editor has the ability to "play the game" within the editor window, and then reset everything back to where it started (which is why the editor needs to know about these scripts in the first place). What I am trying to achieve is basically a "reload script" button in the editor that will recompile and load the script class associated with the level being edited and, when the user presses the "play" button, create an instance of the most recently compiled script. The upshot of which will be a rapid edit-test workflow within the editor (instead of the alternative - which is to save the level, close the editor, recompile the solution, launch the editor, load the level, test). Now I think I have worked out a potential way to achieve this - which itself leads to a number of questions (given below): Compile the collection of `.cs` files required for a given level (or, if need be, the whole `levels.dll` project) into a temporary, unique-named assembly. That assembly will need to reference `engine.dll`. How to invoke the compiler this way at runtime? How to get it to output such an assembly (and can I do it in memory)? Load the new assembly. Will it matter that I am loading classes with the same name into the same process? (I am under the impression that the names are qualified by assembly name?) Now, as I mentioned, I can’t use AppDomains. But, on the other hand, I don’t mind leaking old versions of script classes, so the ability to unload isn’t important. Unless it is? I’m assuming that loading maybe a few hundred assemblies is feasible. When playing the level, instance the class that is inherited from LevelController from the specific assembly that was just loaded. How to do this? And finally: Is this a sensible approach? Could it be done a better way? UPDATE: These days I use a far simpler approach to solve the underlying problem.