Because of the way that the Heat tool works, it's usually a very good idea to
not use it on already registered binaries. If your build process is registering
your binaries, consider unregistering or even suppressing the registration in
the first place (if possible).
"Hoover, Jacob" wrote:
Ok
Ok, regfree won't work for you. By chance do any of the other binaries refer to
your shell extension?
You should be able to unregister the one in the debug folder by using regasm.
On Jul 27, 2013, at 12:45 PM, "Marco Tognacci" wrote:
> I need to register this dll for registering a shell exten
I need to register this dll for registering a shell extension to provide custom
preview for my custom file extension.My setup project is contained in the my
application project folder, but I compile it with a stand alone solution, where
I'm refer to the building folder of my Application, Release
Is your DLL project output set to register for COM interop? Are you building
your install as part of the solution containing the source projects? Have you
ensured your assembly is not registered prior to building the installer project?
Have you tried to manually run heat against the release fold
I have build it first on Debug mode and then on Release. Could be that the
first time Hear register the dll in the Debug folder and then the second time
instead of register the dll in the Release folder it it return the path of the
dll in the debug folder because in the systerm is register the o
5 matches
Mail list logo
