Hi,

I understand that if you want multiple win32 icons in a .NET
application (so that, e.g., Windows Explorer can see them), you have
compile an .rc to an .res with rc.exe, then use the /win32res: option
for either csc.exe or al.exe to link the .res into the assembly.
However I really can't believe there's no way to do this from within
the IDE, even it means using al.exe in a post-build event to relink the
assembly (effectively discarding the one that is created by default).
The question is, is there a reasonable way to determine what the
command line to al.exe should be based on the files in your .NET
project?  Is there even a way to get verbose compiler/linker output
under VS.NET to see how they are being called?

If not, what alternatives are there?  I know there are freeware
utilities that can rebind .res files into existing .exes, but I haven't
tested whether they work with .NET assemblies.  Presumably it wouldn't
be hugely difficult to write one, but I'm not particularly keen on
reinventing the wheel.

Are you using VS2005? If you are, I think you can just add a property
to the csproj file to make it work (using a text editor, since the
option isn't exposed in the IDE).


Mattias

Mattias Sjögren wrote:
Still stuck with VS 2003 at this point, and there doesn't seem to be
anywhere in the .csproj file to specify command line parameters for
csc.exe or al.exe.

Why Assembly.Load get returns wrong assembly.
How many people have .NET 2.0?
x86 vs x64
Accessing Shared Properties of a Parent Windows App from Class Lib
Question about ReaderWriterLock