Add in loads (but does not reach OnConnection) and then Outlook shuts down

I have an add-in that another developer recently had to rebuild.
I seem to be unable to launch it in debug.
I am using VS 2003 and Outlook 2003.

I have used fuslog to detect what assemblies are loading and I can see that
the addin itself loads (along with two other supporting dlls). Outlook opens
up, and immediately shuts down again. I do not get any error messages and
there is nothing in the eventlog. When I re-open Outlook manually (rather
than useing VS to start it) I get told that the Addin did something bad and
do I want to disable it.

Can anyone suggest where the problem may lie? I am assuming it must be
something with the class that is doing the connecting, but I cannot see what
it is.

Thanks
Saira

Is the correct version of the framework being used in the project and is
that version installed on the test computer?

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"Saira" <Saira@BayonetVentures.com> wrote in message
news:u%238N3kYiGHA.1324@TK2MSFTNGP04.phx.gbl...
>I have an add-in that another developer recently had to rebuild.
> I seem to be unable to launch it in debug.
> I am using VS 2003 and Outlook 2003.
>
> I have used fuslog to detect what assemblies are loading and I can see
> that the addin itself loads (along with two other supporting dlls).
> Outlook opens up, and immediately shuts down again. I do not get any error
> messages and there is nothing in the eventlog. When I re-open Outlook
> manually (rather than useing VS to start it) I get told that the Addin did
> something bad and do I want to disable it.
>
> Can anyone suggest where the problem may lie? I am assuming it must be
> something with the class that is doing the connecting, but I cannot see
> what it is.
>
> Thanks
> Saira
>

Fuslog shows that 1.1 is loading up correctly.
I do have 2.0 on this machine, but it does not seem to have caused a problem
thus far.

"Ken Slovak - [MVP - Outlook]" <kenslovak@mvps.org> wrote in message
news:%23XSfGrZiGHA.4416@TK2MSFTNGP02.phx.gbl...
> Is the correct version of the framework being used in the project and is
> that version installed on the test computer?
>
> --
> Ken Slovak
> [MVP - Outlook]
> http://www.slovaktech.com
> Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
> Reminder Manager, Extended Reminders, Attachment Options
> http://www.slovaktech.com/products.htm
>
>
> "Saira" <Saira@BayonetVentures.com> wrote in message
> news:u%238N3kYiGHA.1324@TK2MSFTNGP04.phx.gbl...
>>I have an add-in that another developer recently had to rebuild.
>> I seem to be unable to launch it in debug.
>> I am using VS 2003 and Outlook 2003.
>>
>> I have used fuslog to detect what assemblies are loading and I can see
>> that the addin itself loads (along with two other supporting dlls).
>> Outlook opens up, and immediately shuts down again. I do not get any
>> error messages and there is nothing in the eventlog. When I re-open
>> Outlook manually (rather than useing VS to start it) I get told that the
>> Addin did something bad and do I want to disable it.
>>
>> Can anyone suggest where the problem may lie? I am assuming it must be
>> something with the class that is doing the connecting, but I cannot see
>> what it is.
>>
>> Thanks
>> Saira
>>
>

The only other things I can think of offhand are security settings for the
addin and whether it's set to run from the same location the developer set
up or from wherever it's actually installed. Have you checked with them
about the problem?

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"Saira" <Saira@BayonetVentures.com> wrote in message
news:OnHMXUkiGHA.412@TK2MSFTNGP05.phx.gbl...
> Fuslog shows that 1.1 is loading up correctly.
> I do have 2.0 on this machine, but it does not seem to have caused a
> problem thus far.