Generally, all kind of business applications have to create documents:
invoices, reports, quotations or similar business correspondences.
Typically, developers author applications that enable end users to
modify text and spreadsheets and to create print-ready documents that
can be sent via e-mail (PDF), fax or my traditional mail.
majority of applications deploy Microsoft® Office to create such
documents. But even Microsoft® does not recommend automating their
end-user software Microsoft® Office:Microsoft® does not
currently recommend, and does not support, Automation of Microsoft®
Office applications from any unattended, non-interactive client
application or component (including ASP, ASP.NET, DCOM, and NT
Services), because Office may exhibit unstable behavior and/or deadlock
when Office is run in this environment.Source: MSDN,
Considerations for server-side Automation of Office.
problems and pitfalls when deploying Microsoft® Office:-Interactivity
with the Desktop
Microsoft® Office is an end-user
application and such applications need to be made visible in order to
work correctly. If an error occurs, an error message might be displayed,
which requires user interaction.-Scalability
Office is designed to provide functionality to a single client. It is
not recommended to automate Microsoft® Office in server-side
applications as it is not scalable.-Stability
Microsoft® Office as a service component on a network server may reduce
the stability of that computer, and therefore may reduce the stability
of your whole network."-Security
Office applications were never intended for server-side use. Therefore,
Microsoft® Office applications do not take into consideration the
security problems that distributed components face."
better way to integrate word processing is by using TX Text Control .NET
Server, built from scratch for such scenarios.
With our partner
GrapeCity, we founded the Document Automation Alliance. The idea is to
provide developers a one-stop competence center to gain information on
how to effectively automate Microsoft® Office documents without
attempting to deploy Microsoft® Office.
Read more about this
joint venture on our dedicated website:http://www.document-automation.net
download our trial version and test our shipped ASP.NET samples today:TX
Text Control Trial VersionsAbout TX Text Control:TX Text Control
originally released in 1991, since then more than 40,000 copies have
been sold. Starting off as a single, small DLL, TX Text Control
has made its
way through 16-bit DLL and VBX versions to today‘s Enterprise edition
with its .NET and ActiveX components. The recent addition to the family,
Control .NET Server
, offers all of TX Text Control
processing functionality in an easy-to-use server-side .NET component.
Customers benefit from these years of experience, large user base, and
at the same time, appreciate developing with a mature, reliable product.Contact Informations:firstname.lastname@example.orgNorth
& South America:
Phone: +1 704-370-0110
877-462-4772 (toll free)Europe:
Phone: +49 421 335 910Asia
Phone: +886 2-2797-8508