Wisej.NET Migration
  • Introduction
  • WinForms to Wisej.NET
    • WinForms Migration First Steps
    • Advanced Topics
      • Statics vs. Session Variables
      • Reporting
      • Office Automation
      • Modal Dialogs
      • Registry Access
      • File Access
    • Optimizations After Migration
      • Alert Boxes
      • Watermarks
      • Tool Buttons
      • Enhanced TabControl
      • Enhanced DataGridView
      • AllowHtml
      • Label Wrapper
      • VirtualScroll
      • Theming
      • Responsive Properties
  • VB6 to Wisej.NET
    • VB6 Migration First Steps
  • Gupta to Wisej.NET
    • SAL Migration First Steps
  • Visual WebGUI to Wisej.NET
    • VWG Migration First Steps
    • VWG Advanced Migration
Powered by GitBook
On this page

Was this helpful?

  1. WinForms to Wisej.NET
  2. Advanced Topics

Office Automation

PreviousReportingNextModal Dialogs

Last updated 2 years ago

Was this helpful?

If your application is using Office Automation, moving it to the Server and installing Office on it looks like a feasible approach at first. But this is not recommended at all, even Microsoft . Office Automation was never designed to run unattended or as a server component. You might end up with error message boxes on the server and stuck processes.

The best way to address this, is to identify which Office components are used and find alternative solutions to work with Office documents (either free or paid).

Here is a (non complete) list of Components that we use successfully in migrated projects

(Excel replacement)

(Word, Excel, Powerpoint, Outlook replacements)

underlines this
Epplus
Aspose