Comments by Kendell (Top 2 by date)

Kendell 26-Sep-12 0:12am View

Perhaps another option would be prevent Outlook from entering my "Copy" into the folder, but I can't seem to find a way to do that.

Kendell 26-Sep-12 0:08am View

Fair questions. I am using a Microsoft pre-defined type, and have no way around that. I _think_ that I need cloning because I need a MailItem Object that is not connected in any way to the original object but is identical in every other way. If I simply use the built-in "Copy" method, it creates a duplicate message in the Outlook folder, which I don't want. In the end, I need the user to be presented with my modified version of the message, yet be able to interact with it as if it were the original message (aka reply, forward, etc., using the Outlook 2010 interface.) The problem with "Deep Cloning," even using manual methods as far as I've been able to find, is that "Outlook.MailItem" does not implement either IClonable or ISerializable, therefore making the strategies I've found useless. I'm hoping that you folks could suggest another strategy. My only other work-around is a huge pain in the you-know-what, and not exactly what I want to do. Worst case, I'll do that.