That is a lot easier than I thought

re: That is a lot easier than I thought

Mark — Thu, 12 Jun 2008 16:19:26 GMT

Wow, that really is a lot easier - thanks very much for the tip!

re: That is a lot easier than I thought

Troels Gram — Sat, 07 Jan 2006 01:14:34 GMT

Any success on finding a work around for this yet?

re: That is a lot easier than I thought

Craig Skibo — Thu, 08 Dec 2005 01:14:48 GMT

No, it should not work that way. I will have somebody look into it to see if there is a workaround.

re: That is a lot easier than I thought

Troels Gram — Sun, 04 Dec 2005 21:53:51 GMT

Hi Craig,

I have satellite assemblies working for addin, but I've noticed that VS2005 only loads them properly if the path in the <assembly> element in the .addin file is rooted. Is this intentional? Loading of the actual addin seem to work if I specifiy the assembly location relative to the .addin file location, but VS2005 can't resolve the satellite dlls (my own resource manager in the addin code resolves the satellite assemblies just fine). It would be really nice to be able to specify the assembly path relative to the .addin location as it simplifies deployment greatly (xcopy style). Alternatively I have to provide an msi with custom actions that replace the assembly path in the .addin file with the absolute installation path.. .