|
|
Hi All,
I have AddIn written with VSTO .net 2.0 platform for Outlook 2003.
The addin is deployed and installed on the machine level so the
registry keys are added under:
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook\Addins"
In some cases, we noticed that when the user aborts the startup
process by shutting down Outlook, the next time he will open OL he
will get the old message:
"do you like to disable addin because it caused a seriuous
problem..."
- and most users press 'OK'.
is there a way to mark an addin as a "Trusted" addin so it never
get's
disabled.
This causes a serious maintenance overhead for our solution and
prevents us from reaching more customers...
Thanks
Evgeny.
|
|
Well, you could get a more serious customer maintenance nightmare on
your hands if you continue to try to load an addin that keep
crashing. As this is generally not a good thing to do, is probably
why there have a been a lack of responses.
But one way I can think of is to make a tiny exe that runs either on
os startup, or on a scheduler, etc. It would check your log file to
make sure that your Addin crash was an isolated event and then finds
where Outlook indicates this a problem addin in the registry and
change it. Once again, though, I'd be concerned about such an
approach.
There are probably some other safer tricks based on logging successful
startup and shutdown.
On Mar 20, 3:49 pm, "j" <Evgeny...[ at ]gmail.com> wrote:
[Quoted Text] > Hi All,
>
> I have AddIn written with VSTO .net 2.0 platform for Outlook 2003.
> The addin is deployed and installed on the machine level so the
> registry keys are added under:
> "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook\Addins"
>
> In some cases, we noticed that when the user aborts the startup
> process by shutting down Outlook, the next time he will open OL he
> will get the old message:
> "do you like to disable addin because it caused a seriuous
> problem..."
> - and most users press 'OK'.
>
> is there a way to mark an addin as a "Trusted" addin so it never
> get's
> disabled.
> This causes a serious maintenance overhead for our solution and
> prevents us from reaching more customers...
>
> Thanks
> Evgeny.
|
|
Thanks JahMic,
[Quoted Text] >Well, you could get a more serious customer maintenance nightmare on
>your hands if you continue to try to load an addin that keep
>crashing.
I absolutely agree with you, however the problem is that crashing
occured ( seldom but may occured ) when user
starts Outlook and then close it after tiny period of time, the AddIn
just starts loading and Outlook is being shut down. In regular work
Outlook is not crashes because of my AddIn.
Any ideas??
|
|
Well, as I mentioned:
make an tiny application, service, or some triggered or scheduled
event.
Scan your logs (that you have made in your addin)
If not smooth shutdown, determine if it's isolated event.
if so, Modify registry settings,
if it's Com, the LoadBehavior setting, i think is changed.
There are probably other places you can find in the registry that
Outlook marks such things,
Hmmn, I remember skimming a post or article that this maybe a hashed
value, If so, you may want to keep a tab on that, so you put it back
to the old value.
Tread carefully.
On Mar 27, 5:09 pm, "j" <Evgeny...[ at ]gmail.com> wrote:
[Quoted Text] > Thanks JahMic,
>
> >Well, you could get a more serious customer maintenance nightmare on
> >your hands if you continue to try to load an addin that keep
> >crashing.
>
> I absolutely agree with you, however the problem is that crashing
> occured ( seldom but may occured ) when user
> starts Outlook and then close it after tiny period of time, the AddIn
> just starts loading and Outlook is being shut down. In regular work
> Outlook is not crashes because of my AddIn.
>
> Any ideas??
|
|
|