Now, I use C# as a kind of scripting language and it works quite well. I use it for scripting within a game, where I load several scripts at once, compile them using the C# Compiler classes and invoke the code of the created assembly. Works fine for me. Furthermore I put the compiled assemblies in a separate AppDomain so I''m even able to unload the scripts, e.g. after a level.
If you have this kind of scripts (i.e. quite static), using the built-in compiler works perfectly.
If you need a more dynamic scripting language, i.e. reacting on user input, I''d suggest the System.Reflection.Emit classes using a dynamic assembly. I haven''t experimented very much with it, bit I''d guess they are faster for high-frequent script input as you can extend an existing assembly instead of always creating a new one.
The only Problem with Reflection.Emit is that you can only emit IL-statements. I would find it very cool if there was a C# to IL parser built in. However it isn''t - or I haven''t found it. What you can do is build your own small scripting language and a parser that can create IL-code and use System.Reflection.Emit to dynamically create runtime-usable types and methods. After all, .NET has a HUGE potential for scripting.

Regards,
Andre (VizOne) Loker