views:

283

answers:

1

I have a resource assembly with image files in it that are built using Resource or Content build action. This makes these files accessible using the Uris. However I cannot find the way to enumerate such resources.
If I set the build action to Embedded Resource it becomes possible to enumerate the files with the following code:

string[] resources = Assembly.GetExecutingAssembly().GetManifestResourceNames();

but it in turn makes these files inaccessible using Uris.

The question is - how to enumerate resources that are compiled with either Resource or Content build action?

NOTE: As Thomas Levesque pointed out it is possible to enumerate such resources by leveraging the AssemblyAssociatedContentFileAttribute, but it seems to only work for WPF Application assemblies and not for class library ones. So the question is still open.

+3  A: 

You can enumerate the AssemblyAssociatedContentFile attributes defined on the assembly :

var resourceUris = Assembly.GetEntryAssembly()
                   .GetCustomAttributes(typeof(AssemblyAssociatedContentFileAttribute), true)
                   .Cast<AssemblyAssociatedContentFileAttribute>()
                   .Select(attr => new Uri(attr.RelativeContentFilePath));

You can also check this page for a way to enumerate BAML resources.


UPDATE : actually the solution above works only for Content files. The method belows returns all resource names (including BAML resources, images, etc) :

    public static string[] GetResourceNames()
    {
        var asm = Assembly.GetEntryAssembly();
        string resName = asm.GetName().Name + ".g.resources";
        using (var stream = asm.GetManifestResourceStream(resName))
        using (var reader = new System.Resources.ResourceReader(stream))
        {
            return reader.Cast<DictionaryEntry>().Select(entry => (string)entry.Key).ToArray();
        }
    }
Thomas Levesque
This only works if the assembly has such attributes set - e.g. WPF application would have it set automatically and only for files built with *Content* build action. In case of ClassLibrary assembly there are no such attributes. And even within the assembly code I cannot find the way to enumerate such resources.
Alex_P
The code in update answers the original question, but still isn't a universal solution :) In case of a class library - it enumerates all resources built with *Content*, *Resource* and *Embedded Resource* build action. But in case of WPF Application it only enumerates resources built with *Embedded Resource* build action. So it seems that in order to enumerate all resources in WPF App the combination of both of the above methods is required.
Alex_P