VSOFTBOX

Why AWordReport uses COM Interop?

Using COM Interop is the only way to provide end users with new unsaved rendered documents in user-familiar Microsoft® Word environment.
AWordReport rendered documents can be interactive. They can use full Microsoft® Word formatting abilities, can include macros, forms, embedded objects e.t.c.
Interop allows custom complex logic implementation thanks to full programmatic access to almost every Microsoft® Word behaviour aspect.

Note.
AWordReport assembly (AWordReport.dll) includes all necessary interop classes so you should not distribute extra dll.

You should keep in mind some limitations of COM Interop approach:

AWordReport may be not perfect as main reporting solution when report generation speed is critical. However, AWordReport uses many tricks and "know-how`s" to achieve maximum possible performance while utilizing Microsoft® Word. Run demo projects to examine the speed!
AWordReport may slow down on large tables in report (especially marked with <#txttable:> tag). See special related article about AWordReport speed tuning.
AWordReport has limited application within server-side multi-threaded environment. It is related to well-known server-side Office Automation problems. However, AWordReport designed to run even in such environment and prevents maximum possible issues by isolating the template file from component instances, suppressing the interactivity with desktop e.t.c.