Icons for File Type associations

[Eric]

I want to use embedded icon resources for my file type associations, but
only the app.ico seems to show up when I go to choose the icons in the
setup File Types editor.

The same thing when I try to use Windows Explorer to view embedded icons in
my compiled EXE.

Does anyone know how to compile such that the icons will show up as
standard resources? Or how to add the icons to the executable after
compilation without breaking anything?

[Mick Doherty]

You can still add standard resource files but you have to Manually compile
the project with the /Win32Resource switch. I've not done it, but I remember
seeing it somewhere in the help files.

"Eric" <ef******@massie-labs.com> wrote in message
news:Xn********************************@206.127.4. 12...

I want to use embedded icon resources for my file type associations, but
only the app.ico seems to show up when I go to choose the icons in the
setup File Types editor.

The same thing when I try to use Windows Explorer to view embedded icons in my compiled EXE.

Does anyone know how to compile such that the icons will show up as
standard resources? Or how to add the icons to the executable after
compilation without breaking anything?

[Eric]

"Mick Doherty"
<EX***********@AND.REMOVE.SQUAREBRACKETS.[mdaudi100#ntlworld.com]> wrote
in news:#Q*************@TK2MSFTNGP10.phx.gbl:
eww. Yeah it's there. But you have to use command line compilation.
Anyone have a better idea?

You can still add standard resource files but you have to Manually
compile the project with the /Win32Resource switch. I've not done it,
but I remember seeing it somewhere in the help files.

"Eric" <ef******@massie-labs.com> wrote in message
news:Xn********************************@206.127.4. 12...

I want to use embedded icon resources for my file type associations,
but only the app.ico seems to show up when I go to choose the icons
in the setup File Types editor.

The same thing when I try to use Windows Explorer to view embedded
icons

in

my compiled EXE.

Does anyone know how to compile such that the icons will show up as
standard resources? Or how to add the icons to the executable after
compilation without breaking anything?

[Miyuki]

Well, so get this, I created a seperate DLL that just has 3 icons in it.
Windows explorer can see the icons in the file when I try to change Icons
from a shortcut properties box.

But when I put the DLL file into VS.NET and add it to my setup project, it
dosn't see ANY of the icons when I choose the DLL file. What's going on?

[Mick Doherty]

You could always use the UpdateResource API(with associated api's) to add a
standard windows Icon Resource to the compiled Executable.

"Eric" <ef******@massie-labs.com> wrote in message
news:Xn********************************@206.127.4. 12...

"Mick Doherty"
<EX***********@AND.REMOVE.SQUAREBRACKETS.[mdaudi100#ntlworld.com]> wrote
in news:#Q*************@TK2MSFTNGP10.phx.gbl:
eww. Yeah it's there. But you have to use command line compilation.
Anyone have a better idea?

You can still add standard resource files but you have to Manually
compile the project with the /Win32Resource switch. I've not done it,
but I remember seeing it somewhere in the help files.

"Eric" <ef******@massie-labs.com> wrote in message
news:Xn********************************@206.127.4. 12...

I want to use embedded icon resources for my file type associations,
but only the app.ico seems to show up when I go to choose the icons
in the setup File Types editor.

The same thing when I try to use Windows Explorer to view embedded
icons

in

my compiled EXE.

Does anyone know how to compile such that the icons will show up as
standard resources? Or how to add the icons to the executable after
compilation without breaking anything?

[Eric]

Check this out, I created a seperate DLL that just has 3 icons in it.
Windows explorer can see the icons in the file when I try to change Icons
from a shortcut properties box.

But when I put the DLL file into VS.NET and add it to my setup project, it
dosn't see ANY of the icons when I choose the DLL file. What's going on?