A
Afshar
Hi there,
What is real difference between using Office Interop Assemblies and
VSTO? I want to do some tasks with Office within .net:
1. Reading an Excel workbook
2. Creating a Word document
3. Sending an email via Outlook
4. ...
I used to use Office Interop Assemblies (Referencing Office Interop
Assemblies and utilize Microsoft.Office.Interop.Outlook namespace) to
complete my tasks. But I have some difficulties. In this approach each
operation leads to load an entire Excel or Word application. So this
is very slow and memory consumer. In some cases that my code
encounters exceptions, the WORD.EXE process remains in memory
forever...
I'm interested if I can Visual Studio Tools for Office (VSTO) to get
rid of these entire nasty problems? If not, is there a better way? I
want to use these codes on a server that many users may want to read
some excel workbooks simultaneously.
Thanks: Afshar
What is real difference between using Office Interop Assemblies and
VSTO? I want to do some tasks with Office within .net:
1. Reading an Excel workbook
2. Creating a Word document
3. Sending an email via Outlook
4. ...
I used to use Office Interop Assemblies (Referencing Office Interop
Assemblies and utilize Microsoft.Office.Interop.Outlook namespace) to
complete my tasks. But I have some difficulties. In this approach each
operation leads to load an entire Excel or Word application. So this
is very slow and memory consumer. In some cases that my code
encounters exceptions, the WORD.EXE process remains in memory
forever...
I'm interested if I can Visual Studio Tools for Office (VSTO) to get
rid of these entire nasty problems? If not, is there a better way? I
want to use these codes on a server that many users may want to read
some excel workbooks simultaneously.
Thanks: Afshar