What are the threading limitations for extended MAPI? For example, is it safe to share the same IMsgStore instance between threads with each thread opening / closing different IMessage instanances. thanks
I usually try to avoid sharing objects other than IMAPISessioon between different threads. If you are planning to use MAPI in anything resembling a multithreaded environment, make sure you are using the Exchange version of MAPI. -- Dmitry Streblechenko (MVP) http://www.dimastr.com/ OutlookSpy - Outlook, CDO and MAPI Developer Tool - "Scott McFadden" wrote in message news:%23kvkAAN%23IHA.4472@TK2MSFTNGP05.phx.gbl... > What are the threading limitations for extended MAPI? For example, is it > safe to share the same IMsgStore instance between threads with each thread > opening / closing different IMessage instanances. > > thanks > > >
Guess I was mainly curious as to which extended MAPI classes / methods are thread safe and which ones aren't. My 2003 server box has Exhcange MAPI installed plus full Office 2007 installed. "Dmitry Streblechenko" wrote in message news:uoXioNN%23IHA.3952@TK2MSFTNGP02.phx.gbl... >I usually try to avoid sharing objects other than IMAPISessioon between >different threads. > If you are planning to use MAPI in anything resembling a multithreaded > environment, make sure you are using the Exchange version of MAPI. > > -- > Dmitry Streblechenko (MVP) > http://www.dimastr.com/ > OutlookSpy - Outlook, CDO > and MAPI Developer Tool > - > "Scott McFadden" wrote in message > news:%23kvkAAN%23IHA.4472@TK2MSFTNGP05.phx.gbl... >> What are the threading limitations for extended MAPI? For example, is >> it safe to share the same IMsgStore instance between threads with each >> thread opening / closing different IMessage instanances. >> >> thanks >> >> >> > >
That's bad. We don't support putting Exchange and Outlook's implementations of MAPI on the same box. No matter how you try to do it, invariably you're gonna end up loading some binaries from one implementation and some from the other. Thread safety is the least of your problems. "Scott McFadden" wrote in message news:ONETtxN%23IHA.4856@TK2MSFTNGP06.phx.gbl... > Guess I was mainly curious as to which extended MAPI classes / methods are > thread safe and which ones aren't. > > My 2003 server box has Exhcange MAPI installed plus full Office 2007 > installed. > > > > > "Dmitry Streblechenko" wrote in message > news:uoXioNN%23IHA.3952@TK2MSFTNGP02.phx.gbl... >>I usually try to avoid sharing objects other than IMAPISessioon between >>different threads. >> If you are planning to use MAPI in anything resembling a multithreaded >> environment, make sure you are using the Exchange version of MAPI. >> >> -- >> Dmitry Streblechenko (MVP) >> http://www.dimastr.com/ >> OutlookSpy - Outlook, CDO >> and MAPI Developer Tool >> - >> "Scott McFadden" wrote in message >> news:%23kvkAAN%23IHA.4472@TK2MSFTNGP05.phx.gbl... >>> What are the threading limitations for extended MAPI? For example, is >>> it safe to share the same IMsgStore instance between threads with each >>> thread opening / closing different IMessage instanances. >>> >>> thanks >>> >>> >>> >> >> > >
Without installing Office 2007, how else can you get the office 2007 IFilters? I don't need Outlook so much as I need the IFilter that it installs. "Stephen Griffin" wrote in message news:%23azKa2V%23IHA.4816@TK2MSFTNGP06.phx.gbl... > That's bad. We don't support putting Exchange and Outlook's > implementations of MAPI on the same box. No matter how you try to do it, > invariably you're gonna end up loading some binaries from one > implementation and some from the other. Thread safety is the least of your > problems. > > "Scott McFadden" wrote in message > news:ONETtxN%23IHA.4856@TK2MSFTNGP06.phx.gbl... >> Guess I was mainly curious as to which extended MAPI classes / methods >> are thread safe and which ones aren't. >> >> My 2003 server box has Exhcange MAPI installed plus full Office 2007 >> installed. >> >> >> >> >> "Dmitry Streblechenko" wrote in message >> news:uoXioNN%23IHA.3952@TK2MSFTNGP02.phx.gbl... >>>I usually try to avoid sharing objects other than IMAPISessioon between >>>different threads. >>> If you are planning to use MAPI in anything resembling a multithreaded >>> environment, make sure you are using the Exchange version of MAPI. >>> >>> -- >>> Dmitry Streblechenko (MVP) >>> http://www.dimastr.com/ >>> OutlookSpy - Outlook, CDO >>> and MAPI Developer Tool >>> - >>> "Scott McFadden" wrote in message >>> news:%23kvkAAN%23IHA.4472@TK2MSFTNGP05.phx.gbl... >>>> What are the threading limitations for extended MAPI? For example, is >>>> it safe to share the same IMsgStore instance between threads with each >>>> thread opening / closing different IMessage instanances. >>>> >>>> thanks >>>> >>>> >>>> >>> >>> >> >> > >
