When using al.exe to create an assembly, you can add a file as a resource to the Assembly by using/embed [Resource. this switch accepts a file (any file) and embeds the file content into the PE file. the manifest manifestresourcedef table is updated to reflect the existence of the resource.
Al.exe also supports the/link [Resource] switch, which also accepts a file containing resources. However, the/link [Resource] switch updates the manifest manifestresourcedef table and filedef table, indicates the resource existence and the file where the resource exists in the Assembly. the resource file is not embedded into the PE file of the Assembly. It exists independently and must be packaged and deployed along with other assembly files.
Like al.exe, csc.exe allows you to merge multiple resources into a single assembly. C # The/resource switch of the compiler embeds the specified resource file into the PE file of the assembly and updates the manifestresourcedef table. the/linkresource switch of the compiler adds an entry to the manifestresourcedef and filedef tables to point to independent resource files.
The last point about the resource is that you can embed the standard Win32 resource into a set of programs. When you use al.exe1_csc.exe, you can use the/win32res switch to specify one. res file path. in addition, you can quickly and easily embed a standard Win32 icon resource into the assembly and specify it by using the/win32icon switch. ICO file path. in Visual Studio, you can add resource files to your Assembly: first, display the properties of the project, and then click the Application tab. A typical reason for embedding an icon is that Windows resource manager can display an icon for a hosted executable file.