microsoft doesn't support dotnet "plugins" good enough

  • Thread starter Thread starter alexl
  • Start date Start date
A

alexl

if my program is an .exe application and I need to reference external
assemblies, no problem. I can embed my manifest as resource 1. But if
my program is itself a "plugin," that is a dll that gets loaded to
another .exe program, there's problems. I can still reference the
external assembly via resource identifier 2, but if it is a com
oriented external assembly I have to either modify the hosting .exe
application's resource manifest, use regsvr32, or I have to play
around with activation contexts. thoughts?
 
Back
Top