> VS from scratch, I can see my command in the IDE but I can never execute them
> because it seems VS cannot load the general purpose assembly. The directory
Are you sure this is the reason for commands not working? Our add-in
also uses multiple assemblies that are stored as DLLs in the same
directory as add-in's main DLL. There is no problem locating them. They
are all in one add-in solution and we didn't do anything special.

Signature
Peter Macej
Helixoft - http://www.helixoft.com
VSdocman - Commenter and generator of class documentation for C#, VB
.NET and ASP .NET code
Jeff MAURY - 02 Oct 2006 13:18 GMT
> > VS from scratch, I can see my command in the IDE but I can never execute them
> > because it seems VS cannot load the general purpose assembly. The directory
[quoted text clipped - 3 lines]
> directory as add-in's main DLL. There is no problem locating them. They
> are all in one add-in solution and we didn't do anything special.
Is is on VS 2005 ? I am pretty sure this is the problem because I used
filemon to track assmebly loading and I saw it tries to load it but can't do
it. How did you package your add-in ?
Jeff MAURY - 02 Oct 2006 14:17 GMT
Peter,
I found the solution: this was because the LoadBehavior flag in my test
.AddIn file was set to 0. Setting it to 1 make the addin to work correctly.
Thanks for the help
Jeff
> > > VS from scratch, I can see my command in the IDE but I can never execute them
> > > because it seems VS cannot load the general purpose assembly. The directory
[quoted text clipped - 6 lines]
> filemon to track assmebly loading and I saw it tries to load it but can't do
> it. How did you package your add-in ?