I am trying to add a managed code custom action via 'stored in the binary table', but the dll assembly i am using references another dll. When the application is run the custom action can't locate the referenced dll. Is there a way to add additional dll's to the binary table so they can be found during the Custom Action execution?
So long as the .dll files you depend on are also managed code, then yes. There's a document around somewhere, but the gist of it is to use the direct editor to add lines to the ISClrWrap table. Each line will have Action_ = action name, Name = Dependency# (where # is replaced with numbers starting at 0; don't skip any!), and the build path to the dependent dll (path variables can be used).
