How Microsoft does it?

[JayvardhanPune]

Dear All,

I am creating a Image Library and want to know what can the best and
standard procedure to do this.

Concept is to have all the images needed by all projects (dlls and
exes) in the product at a central place (in a single DLL) making it
easy to distribute and maintain.

There are 2 ways of doing this.
1) Creating a new project, add all the images to it using "Add Existing
Item" and set Build Action=Embeded Resource for each image.
OR
2) Creating a new project>Add new Item>Resources File and then adding
all the images to it and setting Build Action=Embeded Resource for each
image. Doing this will provide me a strongly typed DLL which will
provide a property like access to all images. But .resx are mainly for
localization. And here I am not localizing images.

My question is what is the standard way of doing this?
Do you guys know pros or cons of any of these methods?
Is anybody there knowing how Microsoft do it??? (When they need to
create an image library)
Any links or articles for this?
Most important is, will the second (2) way will have any negative
effect on start up time?

[Peter Bromberg [C# MVP]]

J,
I am not sure if there really is a "standard" or "best practices" way of
doing this. I do know, however, that if you create an assembly with all your
images embedded as resources, perhaps with a class that has a utility method
in it to extract them, that would be quite usable and extensible.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"JayvardhanPune" wrote:

Dear All,

I am creating a Image Library and want to know what can the best and
standard procedure to do this.

Concept is to have all the images needed by all projects (dlls and
exes) in the product at a central place (in a single DLL) making it
easy to distribute and maintain.

There are 2 ways of doing this.
1) Creating a new project, add all the images to it using "Add Existing
Item" and set Build Action=Embeded Resource for each image.
OR
2) Creating a new project>Add new Item>Resources File and then adding
all the images to it and setting Build Action=Embeded Resource for each
image. Doing this will provide me a strongly typed DLL which will
provide a property like access to all images. But .resx are mainly for
localization. And here I am not localizing images.

My question is what is the standard way of doing this?
Do you guys know pros or cons of any of these methods?
Is anybody there knowing how Microsoft do it??? (When they need to
create an image library)
Any links or articles for this?
Most important is, will the second (2) way will have any negative
effect on start up time?