You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 0786294
Browse filesBrowse the repository at this point in the historyBrowse files
> This material applies to Windows desktop applications. For information about resources in Universal Windows Platform apps, see [Defining App Resources](/windows/uwp/app-resources/).
11
12
>
12
-
> For information on adding resources to managed projects, please see [Resources in Desktop Apps](/dotnet/framework/resources/index) in the *.NET Framework Developer's Guide*. For information on manually adding resource files to managed projects, accessing resources, displaying static resources, and assigning resource strings to properties, see [Creating Resource Files for Desktop Apps](/dotnet/framework/resources/creating-resource-files-for-desktop-apps). For information on globalization and localization of resources in managed apps, see [Globalizing and Localizing .NET Framework Applications](/dotnet/standard/globalization-localization/index).
13
+
> For information on adding resources to managed projects, see [Resources in Desktop Apps](/dotnet/framework/resources/index) in the *.NET Framework Developer's Guide*. For information on manually adding resource files to managed projects, accessing resources, displaying static resources, and assigning resource strings to properties, see [Creating Resource Files for Desktop Apps](/dotnet/framework/resources/creating-resource-files-for-desktop-apps). For information on globalization and localization of resources in managed apps, see [Globalizing and Localizing .NET Framework Applications](/dotnet/standard/globalization-localization/index).
13
14
>
14
15
> Since projects in .NET programming languages do not use resource script files, you must open your resources from **Solution Explorer**. You can use the [Image editor](../windows/image-editor-for-icons.md) and the [Binary editor](binary-editor.md) to work with resource files in managed projects. Any managed resources you want to edit must be linked resources. The Visual Studio resource editors do not support editing embedded resources.
15
16
@@ -23,7 +24,7 @@ The term "resource file" can refer to a number of file types, including:
23
24
24
25
- A header file generated by the development environment, for example Resource.h, that is referred to from an .rc file.
25
26
26
-
Resources can also be found in [other file types](../windows/editable-file-types-for-resources.md) such as .exe, .dll, and .res files. You can work with resources and resource files from within your project and with those that are not part of your current project. You can also work with resource files that were not created in the development environment of Visual Studio. For example, you can:
27
+
Resources are also found in [other file types](../windows/editable-file-types-for-resources.md) such as .exe, .dll, and .res files. You can work with resources and resource files from within your project and the ones that aren't part of your current project. You can also work with resource files that weren't created in the development environment of Visual Studio. For example, you can:
27
28
28
29
- Work with nested and conditionally included resource files.
29
30
@@ -33,38 +34,78 @@ Resources can also be found in [other file types](../windows/editable-file-types
33
34
34
35
- Include shared or read-only identifiers (symbols) that can't be modified by the development environment.
35
36
36
-
- Include resources in your executable (.exe) file that don't require editing (or that you don't want to be edited) during your current project, such as resources that are shared between several projects.
37
+
- Include resources in your executable (.exe) file that don't require editing (or that shouldn't be edited) during your current project, such as shared resources between several projects.
37
38
38
39
- Include resource types not supported by the development environment.
39
40
40
-
This section covers:
41
+
You can open the following types of files and edit the resources they contain:
41
42
42
-
-[Creating a New Resource Script File](../windows/how-to-create-a-resource-script-file.md)
43
+
|File name|Description|
44
+
|---------------|-----------------|
45
+
|.rc|Resource script files.|
46
+
|.rct|Resource template files.|
47
+
|.res|Resource files.|
48
+
|.resx|Managed resource files.|
49
+
|.exe|Executable files.|
50
+
|.dll|Dynamic-link library files.|
51
+
|.bmp, .ico, .dib, and .cur|Bitmap, icon, toolbar and cursor files.|
43
52
44
-
-[Creating a New Resource](../windows/how-to-create-a-resource.md)
53
+
The Visual Studio environment works with and affects the files shown in the following table during your resource editing session:
45
54
46
-
-[Viewing Resources in a Resource Script File](../windows/how-to-open-a-resource-script-file-outside-of-a-project-standalone.md)
55
+
|File name|Description|
56
+
|---------------|-----------------|
57
+
|Resource.h|Header file generated by the development environment; contains symbol definitions. (Include this file in source control.)|
58
+
|Filename.aps|Binary version of the current resource script file; used for quick loading.<br /><br /> The resource editors don't directly read .rc or resource.h files. The resource compiler compiles them into .aps files, which are consumed by the resource editors. This file is a compile step and only stores symbolic data. As with a normal compile process, information that isn't symbolic (for example, comments) is discarded during the compile process. Whenever the .aps file gets out of synch with the .rc file, the .rc file is regenerated (for example, when you Save, the resource editor overwrites the .rc file and the resource.h file). Any changes to the resources themselves will remain incorporated in the .rc file, but comments will always be lost once the .rc file is overwritten. For information on how to preserve comments, see [Including Resources at Compile Time](../windows/how-to-include-resources-at-compile-time.md). (Typically, you shouldn't include the .aps file in source control.)|
59
+
|.rc|Resource script file that contains script for the resources in your current project. This file is overwritten by the .aps file whenever you save. (Include this file in source control.)|
47
60
48
-
-[Opening a Resource Script File in Text Format](../windows/how-to-open-a-resource-script-file-in-text-format.md)
61
+
This section covers how to:
49
62
50
-
-[Including Resources at Compile Time](../windows/how-to-include-resources-at-compile-time.md)
-[Include Resources at Compile Time](../windows/how-to-include-resources-at-compile-time.md)
55
68
56
-
-[Importing and Exporting Resources](../windows/how-to-import-and-export-resources.md)
69
+
## Manifest resources
57
70
58
-
-[Editable File Types for Resources](../windows/editable-file-types-for-resources.md)
71
+
In C++ desktop projects, manifest resources are XML files that describe the dependencies that an application uses. For example, in Visual Studio, the MFC wizard-generated manifest file defines which of the Windows common control DLLs the application should use, version 5.0 or 6.0:
59
72
60
-
-[Files Affected by Resource Editing](../windows/files-affected-by-resource-editing.md)
For a Windows XP or Windows Vista application, the manifest resource not only specifies that the application use the most current version of the Windows common controls, v6.0, as seen above, but it also supports the [Syslink control](/windows/desktop/Controls/syslink-overview).
90
+
91
+
To view the version and type information contained in a manifest resource, you can open the file in an XML viewer or in the Visual Studio text editor. If you open a manifest resource from [Resource View](../windows/resource-view-window.md), the resource will open in binary format. To view the contents of a manifest resource in a more viewable format, you must open the resource from **Solution Explorer**.
92
+
93
+
To open a manifest resource, choose from the following steps:
94
+
95
+
- For text editor, with your project open in **Solution Explorer**, expand the **Resource Files** folder and double-click the .manifest file.
96
+
97
+
- For another editor, in **Solution Explorer**, right-click the .manifest file and choose **Open With...** from the shortcut menu. In the **Open With** dialog box, specify the editor you would like to use and select **Open**.
98
+
99
+
> [!NOTE]
100
+
> You can only have one manifest resource per module.
0 commit comments