Strange problem with ICommandImpl class

egauthier

Hello

I'm encountering a very strange problem on a custom command for FileSite.

I've written a class in C#, implementing interface ICommandImpl, and set the appropriate registry key to add this class as a FileSite command in the FileSite menu.

Basically, the problem is that the code that is in the execute part of the class is not called when actionning the command.

I know that because I've added log information in the constructor, initialize and execute methods of that class, and I can see that both constructor and initialize methods are successfully run, but the code in the execute method is never called.

What is even more weird is that it is perfectly working on some environment (filesite 8.2 sp1p4 with outlook 2007), I mean in this case the execute part is correctly called.
However in another environment (outlook 2003 + Filesite 8.2, unknown subversion), it's not working, that is to say, initialize and constructor of the ICommand are called, but the code in execute method is not called.

Is there any reason why the execution of the code in the execute method of a custom ICommand might be blocked ? What could cause this behavior ?

Just to mention, there is no code in the Update method (but that doesn't change anything I guess), and I don't think there's any exception raised in any of initialize or constructor methods.

any idea on what could cause this error ?
What could I do to investigate the possible reason of this problem ?

Any help will be highly appreciated.

Thanks a lot in advance.

Etienne

jny

Hello I'm encountering a very strange problem on a custom command for FileSite. I've written a class in C#, implementing interface ICommandImpl, and set the appropriate registry key to add this class as a FileSite command in the FileSite menu. Basically, the problem is that the code that is in the execute part of the class is not called when actionning the command. I know that because I've added log information in the constructor, initialize and execute methods of that class, and I can see that both constructor and initialize methods are successfully run, but the code in the execute method is never called. What is even more weird is that it is perfectly working on some environment (filesite 8.2 sp1p4 with outlook 2007), I mean in this case the execute part is correctly called. However in another environment (outlook 2003 + Filesite 8.2, unknown subversion), it's not working, that is to say, initialize and constructor of the ICommand are called, but the code in execute method is not called. Is there any reason why the execution of the code in the execute method of a custom ICommand might be blocked ? What could cause this behavior ? Just to mention, there is no code in the Update method (but that doesn't change anything I guess), and I don't think there's any exception raised in any of initialize or constructor methods. any idea on what could cause this error ? What could I do to investigate the possible reason of this problem ? Any help will be highly appreciated. Thanks a lot in advance. Etienne

Have you tried the following:

- at run-time, add a messagebox inside the ICommand_Execute() function.
- in debug mode, set a break point inside the ICommand_Execute() function.
- check that the command name is the same as the progid you add to the registry key setting.

It sounds like your ICommand_Update function isn't the problem since you're able to invoke the corresponding menu item; this indicates the status is set to ActiveCommand.