Jeremy said:
You could try creating manifests for the Office executables your add-in will
be used with. I have made this work with certain executables, but it does
not always look quite right.
Actually that's great, and shows just how easily I get stuck looking at
things the wrong way. I haven't hooked it up to COM yet because most of
the functionality isn't in place yet. But I'm testing via a console app,
and making a manifest for *it* was all I needed to do.
ConsoleTests.exe.manifest has almost nothing in it, but it makes all the
difference. Go figure
Don't know if this will display correctly, but...:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="X86"
publicKeyToken="6595b64144ccf1df"
language="*" />
</dependentAssembly>
</dependency>
</assembly>