GAC vs local copy

[David Thielen]

Hi;

In the post
http://msdn.microsoft.com/newsgroup....sdk&mid=589e3a7e-254f-46d9-89ca-67490a09475d
I am told I need to put the DLLs for my Word AddIn in the GAC. However, I was
earlier told here that for a Word AddIn do NOT put it in the GAC.

So how can I solve this problem?

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm

 

[Steven Cheng[MSFT]]

Hello Dave,

From the former thread you refered, some office team engineer suggest you
not put add-in assembly into GAC, have they provided you some further
information or document on why that is not recommended? Following the
standard .net framework assembly loading policy and your scenario(different
version of the same strong-named assemblies will be used by multiple
applications), put in GAC is the reasonable way to make all the assemblies
visitble to applications on that machine.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead



This posting is provided "AS IS" with no warranties, and confers no rights.

 

[David Thielen]

Hi;

Here is a post about placement:
http://groups.google.com/group/micr...=st&q=gac+word+AddIn&rnum=13#90b17ab33ef344cd

I also received an email from a developer in the word group telling me to
keep the AddIn out of the GAC because I use a shim for security signing. But
rereading his email he may have meant just the AddIn and not the other DLLs.

So...

For an AddIn that has a C++ shim, what should go in the GAC? The AddIn, the
3rd party .NET DLLs? both? neither?

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm

 

[pavan]

Your shim and add-in dlls should under be the same folder. Shim dll is
registered, so it should not be moved around (considering that you want
registration to be a one time process). So you shouldn't move your
add-in dll either. Thus, I don't think neither of these dlls go into
GAC.

For the remaining dlls, it's your choice. If you want you can still put
all the referenced dlls under the same folder as the add-in dll or put
them in GAC and make them shared, in case if any other applications
want to use them.

Hope this helps,
Regards,
Pavan