>

> This is VB6 code, we started the port to .net last month, but had to put
> out some fires. In researching my options for the port (still a little on
> the fence, but leaning more toward shared AddIn than VSTO) I read about
> the reference leak problem with multi-level object references...
> inopportune timing, because to me something like Item.UserProperties.Add()
> is an intuitive construct. Anyway, I'm pretty sure there was at least
> some of it that was affecting my code, I was seeing occasional "can't
> save, do you want to save a copy..." prompts that were confusing,
> especially for inherently read-only items like inbox emails. I resolved
> them, though how much via explicit object resolution I'm uncertain.
>
> Anyway, before I lose sight of it... how does any/all of this have to do
> with Outlook deciding to gray the Print Preview menu, but not the Print
> menu? Clearly the item is printable, why does it care whether it's
> rendering to a display device context (DC) versus a printer DC?
> Previewing should be slightly less complicated than printing, one less
> device dependency. It makes no sense to me.
>
> It's not a big deal, I have PDFMachine, so I don't have to waste any
> paper...
>
> That it doesn't happen with plain-text items would seem to reinforce the
> premise that leaked references shouldn't impact this -- I'm not saying
> they don't, but they damn well shouldn't, rendering for print shouldn't
> care about saved/unsaved/multiple references, it should just read what's
> available and render.
>
> -MM
>
>
>
>
>
>
>
>