Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » OOM.NET   (RSS)
Thursday, June 12, 2008 2:43 PM

OOM.NET: Part 5 - Event Planning

Plan For What You Can Control One of the common scenarios in OOM programming in managed code that required calling GC.Collect() was handling events.  As has been discussed earlier in this series, item references need to be released before they go
Posted by mstehle | 1 Comments
Friday, March 14, 2008 10:01 AM

OOM.NET: Part 4 - Don't Thread On Me

Patrick posted a discussion of multithreading with Outlook Object Model and why it doesn't help to make OOM calls on a seperate thread... "Outlook Object Model is run in a STA COM server. This means that all OOM calls are executed on the main thread...You
Posted by mstehle | 1 Comments
Monday, February 18, 2008 4:13 PM

OOM.NET: Part 3 - Back to the Basics, MSDN Must Reads

The Outlook Developer Reference on MSDN has great information on .NET and COM interop which I would consider a prerequisite to any managed code development with Outlook Object Model. It simply isn't enough to know how to accomplish tasks with OOM or to
Posted by mstehle | 1 Comments
Friday, December 07, 2007 2:50 PM

OOM.NET: Part 2 - Outlook Item Leaks

Outlook item leaks are the most common OOM with .NET issues that we see and I’ve debugged enough of them to compile this list of the four basic mistakes that contribute to item leaks. An “item leak” is most commonly seen as an item that won’t refresh
Posted by mstehle | 4 Comments
Thursday, December 06, 2007 5:12 PM

OOM.NET: Part 1 - Introduction and Why Events Stop Firing...

OOM.NET is not a special API set that was created in managed code.  It is the name I've given to a series of posts I'll do about the “gotchas” of Outlook Object Model development in .NET.  I've compiled some notes over time of the
Posted by mstehle | 3 Comments
Thursday, May 31, 2007 2:56 PM

FYI: COM Interop Changes in .NET Framework 2.0 and Outlook Object Model

If you have seen the error below when using objects from OOM in .NET 2.0 code then the information that Mason posted recently will explain a lot. The key to avoiding this error is to use the interfaces in OOM not the CoClasses. Mason explains why in his
Posted by mstehle | 0 Comments
 
Page view tracker