Requirements for non-destructive HTML5 app compilation

I could identify the problem, its basically related to the way the DBCompiler cleans up the DialogScriptAssemblies before a full compile starts on a non-productive database. Hence i will handle this as a SR.

I could identify the problem, its basically related to the way the DBCompiler cleans up the DialogScriptAssemblies before a full compile starts on a non-productive database. Hence i will handle this as a SR.

I ran into the very same problem.. Did you get any advice or fix for that?

Hello, not really.

Some information from dev in that regard was that QBM\HtmlDevelopment\Compiler enabled is required for a HTML application to work. Therefore a full compile (which removes the HTML5 assemblies) implicitly creates new ones depending on the ConfigParm. So there is no chance to keep the assemblies without recompiling HTML5 applications during full compile. In our case, we can kind of "work around" this behavior as we are using an automatic deployment approach which is based on certain CMDLets (e.g. DBTransporterCMD.exe & DBCompilerCMD.exe). By using the DBTransporterCMD.exe you can at least suppress compilations implicitly started during transport and start a more controlled compilation afterwards.

Thank you, Daniel