C# Excel Add-in works on some machines, but then not others

[aaronfude]

Hi,

I've working on an Excel Add-in written is C# that someone else has
started and I have been modifying. It is based on the .Net Framwork
2.0

All of a sudden, the add-in stopped working on my machine and several
others, but still works on a bunch of other ones.

The symptoms are these:
The plugin installs and when you go Tools->Add-Ins->Automation it is
there. Furthermore, upon selecting it, it adds itself to the list of
add-ins. *
However*, the functions defined in it are unavailable in Excel. If you
try to use one, you get "#NAME?". If you select the function dialog,
the functions are not on the list, nor is the add-in under "Or select
a category".

We are at a total loss and any help would be greatly appreciated. This
is really killing our productivity.

Thank you!

Aaron Fude

[aaronfude]

Hi,

I would appreciate any suggestions whatsoever!

Aaron Fude

[Eric]

On Apr 5, 8:05 am, [e-mail] wrote:

I would appreciate any suggestions whatsoever!

Since you put it that way, I'll venture a guess. Could it be related
to security settings on the PC? I know you have to take extra measures
to allow a PC to run a VBA script inside a spreadsheet.

If your networking people are anything like ours, they probably
decided to lock down some permissions without coordinating first.
That's a weekly occurance at my company :-(

Eric

[aaronfude]

!!!!Yes!!!!

Thank you Eric.

This is some kind of a glitch, because my Macro Security was already
set to Low and I had checkmarks for "Trust all installed templates and
add-ins" and "Trust access to Visual Basic" projects, but unchecking
those and then rechecking them revived by c-sharp Add-in!

Once again, thank you. This has taken months!

(Was there a more systematic way to catch something like this? Is
there an error log or console of some kind?

Aaron

[Eric]

On Apr 7, 12:29 am, [e-mail] wrote:

(Was there a more systematic way to catch something like this? Is
there an error log or console of some kind?

Maybe the Windows Event Log had some kind of useful tips about a
security problem? But there's a good chance it didn't show anything
useful. Addins in general are difficult to debug.

Eric