M
MAFr
Local version of the program properly creates (or attaches to already
running) outlook application object and quits (when created- my logic) it
using quit() method.
The same scheme doesn't work as aspnet (i.e. it can not recognize running
outlook application, therefore, always creates new one, and doesn't not quit
it after calling quit() method for created object).
Additional info:
1. For aspnet application in machine.config file (processModel record) I
replaced machine/AutoGenerate with my userid/passwd.
2. To catch running outlook instance I use
System.Runtime.InteropServices.Marshal.GetActiveObject
("Outlook.Application") which works fine for local version and doesn't work
for aspnet.
Help/prompt would be appreciated.
Thanks in advance.
running) outlook application object and quits (when created- my logic) it
using quit() method.
The same scheme doesn't work as aspnet (i.e. it can not recognize running
outlook application, therefore, always creates new one, and doesn't not quit
it after calling quit() method for created object).
Additional info:
1. For aspnet application in machine.config file (processModel record) I
replaced machine/AutoGenerate with my userid/passwd.
2. To catch running outlook instance I use
System.Runtime.InteropServices.Marshal.GetActiveObject
("Outlook.Application") which works fine for local version and doesn't work
for aspnet.
Help/prompt would be appreciated.
Thanks in advance.