Release web site should generate release assemblies

Maybe that switch could be read from <compilation debug="true|false"> section in web.config.

But then spark would be tied to asp.net (and might not be well suited to be used as custom file generator, see replacing NVelocity). Of course, code could check whether it is in web context, and should use web.config, or some custom parameter provider.

Another option is to introduce a custom configuration section, that would provide all required parameters to spark.

Possible solution (as far as I rememeber HttpContext.Current is null when outside asp.net context):

if (HttpContext.Current != null)
{
    CompilationSection configSection = (CompilationSection)WebConfigurationManager.GetSection("system.web/compilation");
    compilerParameters.IncludeDebugInformation = configSection.Debug;
}
else
{
    compilerParameters.IncludeDebugInformation = true;
}

I believe there was a problem with use of the asp.net debug that the AspView? engine for MonoRail? already encountered... I believe it was iis6 and iis7 each have their own configuration section, so you'd also need to find out which one was in effect.

I also realized that the release build of spark is what most people will be using when they debug. So using that would make no sense at all!

I think I'm leaning towards having an optional custom configuration section.

Debug compile is off by default. It can be enabled with debug="true" in the spark config.

<configSections>
  <section name="spark" type="Spark.Configuration.SparkSectionHandler, Spark"/>
</configSections>
<spark>
  <compilation debug="true"/>
</spark>