Thought about that but don't want to have that kind of trouble. Do the
publish in the first run or until it is needed is better idea.

"Ken Slovak - [MVP - Outlook]" wrote in message
...
In managed code setting an object to null does not necessarily release the
RCW, that's only after the GC runs at some undetermined time. To fully
release objects call Marshal.ReleaseComObject() on the object and if
necessary call it in a loop until the return int is 0.

FWIW, if I have an addin I do my form publishing in the addin code on
first run and never during installation.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm


"Jason" wrote in message
...
Did not work. All variables were set to null before app.QUit() was
issued. I even used scope

Outlook.Application app = new Outlook.Application();

{
...
}

app.Quit();

System.Runtime.InteropServices.Marshal.ReleaseComO bject(app);


May be MSI package and installer class work differently.

Anyway I gave up. I moved the publish function to the setup form inside
add-in. User has to provide some info before they can use the add-in.