Say, you have a custom control MyControl in the namespace MyNamespace, create a bmp file MyControl.bmp following the above rules. Add this file to your project at the top-level and make it an embedded resource. The project’s default namespace should be MyNamespace.
If the control’s namespace and the project’s default namespace don’t match then move the bitmap to appropriate subfolders so that they match. If this is not possible, typically when the namespaces are not related at all then you cannot use this technique, use instead one of the techniques below using the ToolboxBitmap attribute.
Create the assembly and the next time you add it to the toolbox the custom image in MyControl.bmp should be available in the toolbox.
This is the easiest technique to implement as it doesn’t require you to use the ToolboxBitmapAttribute in your type definition.Technique 2: Use ToolboxBitmap attribute.
Example 1:Use a bitmap (not icon) in the embedded resource with the same name as the type.
Default Assembly Namespace: "MyAssemblyNamespace"In the above scenario the runtime will look for a embedded bmp file of name MyCustomType.bmp in the project’s root directory. Note that the default namespace and the type’s namespace match.
Example 2:If you want your icons in sub-directories then change the attribute like this: or where the bmp or ico file (yap, now, when you explicitly specify the resource, you can use an ico file) is in a sub-directory called "ToolboxIcons".
Example 3:Sometimes your type’s namespace and the default assembly namespace may be unrelated, in which case you have to use a different type that has the same namespace as the default assembly namespace to scope the embedded image file.
Default namespace: "MyAssemblyNamespace"In this case the runtime will look for the above resource at the top-most directory. If your icons were in a subdirectory named "ToolboxIcons" then the attribute would look like this: