You may want to GAC your assembly on the users' machines.
--
Bryan Phillips
MCSD, MCDBA, MCSE
Blog: http://bphillips76.spaces.live.com
> You may want to GAC your assembly on the users' machines.
>
> --
> Bryan Phillips
> MCSD, MCDBA, MCSE
> Blog: http://bphillips76.spaces.live.com
And this will make it so that the xls file will invoke the assembly?
Right now, I'm not getting any kind of error. It's just not
invoking. I would think that if it were an issue that the GAC would
solve, that I'd be getting an error. In this case, Excel acts as if
it isn't even aware that the assembly exists.
Bob Eaton - 23 Mar 2007 03:54 GMT
Isn't "The customization assembly could not be fond or could not be loaded."
an error?
I have no idea whether this is your problem (not knowing much about VSTO),
but the way .Net normally works is that the assembly must be a) in the same
folder as the exe calling it (i.e. C:\PF\MO\Office11...), b) the Global
assembly cache (where it can find it easily enough), or c) you must register
the assembly with "Regasm /codebase" so that it adds the assembly location
to the registry.
Bob
>> You may want to GAC your assembly on the users' machines.
>>
[quoted text clipped - 8 lines]
> solve, that I'd be getting an error. In this case, Excel acts as if
> it isn't even aware that the assembly exists.