From a high-level view, there are two things you need to do:
- P/Invoke the Activation Context API, and use it to load the manifest that your reg-free COM information is in (usually it's Native.[assemblyname].manifest) during the startup of your VSTO add-in.
- The VSTO build process will not include your Native.[assemblyname].manifest in the Application Manifest, so you'll have to add it yourself. Since I wrote it at work I can't share our method, but we ended up creating a command-line tool that runs as a post-build step and manually adds the file reference using XmlDocument, and re-hashes and re-signs everything.
No comments:
Post a Comment