A refined version of the original EmbeddedResourceAccessGenerator by ChristophHornung

Improvements in the EmbeddedResourceAccessGenerator:

• Fixed a bug when the generator generates code for all AdditionalFiles, not EmbeddedResources only. This means that the original EmbeddedResourceAccessGenerator is incompatible with all three generators and must be removed before adding those generators.
• Removed properties from the EmbeddedResources class, because it's an anti-pattern to create disposable resources on every get property access.
• The GetReader method now creates the StreamReader with the option leaveOpen: false. It disposes the stream together with the StreamReader.
• Added synchronous and asynchronous extension methods ReadAllText, ReadAllTextAsync, ReadAllBytes, ReadAllBytesAsync.

EmbeddedResourceAccessGenerator

The Raffinert.EmbeddedResourceAccessGenerator is a code generator to allow easy access to all embedded resources.

Usage

Get the nuget package here.

After referencing the Raffinert.EmbeddedResourceAccessGenerator nuget the code generation will automatically create a class EmbeddedResources in the root namespace of the project.

Together with the generated EmbeddedResource enumeration there are several options to access embedded resources:

E.g. for a Test.txt embedded resource in the TestAsset folder:

• Via enum access through the EmbeddedResource enum:

    // Via the generated extension methods on the enum
    using Stream s = EmbeddedResource.TestAsset_Test_txt.GetStream();
    using StreamReader sr = EmbeddedResource.TestAsset_Test_txt.GetReader();
    string text = EmbeddedResource.TestAsset_Test_txt.ReadAllText();
    string textAsync = await EmbeddedResource.TestAsset_Test_txt.ReadAllTextAsync(CancellationToken.None);
    byte[] bytes = EmbeddedResource.TestAsset_Test_txt.ReadAllBytes();
    byte[] bytesAsync = await EmbeddedResource.TestAsset_Test_txt.ReadAllBytesAsync(CancellationToken.None);

• Via enum access through the EmbeddedResource[FolderName] enum:

    // Via the generated extension methods on the enum
    using Stream s = EmbeddedResource_TestAsset.Test_txt.GetStream();
    using StreamReader sr = EmbeddedResource_TestAsset.Test_txt.GetReader();
    string text = EmbeddedResource_TestAsset.Test_txt.ReadAllText();
    string textAsync = await EmbeddedResource_TestAsset.Test_txt.ReadAllTextAsync(CancellationToken.None);
    byte[] bytes = EmbeddedResource_TestAsset.Test_txt.ReadAllBytes();
    byte[] bytesAsync = await EmbeddedResource_TestAsset.Test_txt.ReadAllBytesAsync(CancellationToken.None);

ContentItemAccessGenerator

The Raffinert.ContentItemAccessGenerator is a code generator to allow easy access to all content files with CopyToOutputDirectory attribute specified as Always or PreserveNewest.

Usage

Get the nuget package here.

After referencing the Raffinert.ContentItemAccessGenerator nuget the code generation will automatically create a class Contents in the root namespace of the project.

Together with the generated Content enumeration there are several options to access content files:

E.g. for a Test.txt content item in the TestAsset folder:

• Via enum access through the Content enum:

    // Via the generated extension methods on the enum
    using Stream s = Content.TestAsset_Test_txt.GetStream();
    using StreamReader sr = Content.TestAsset_Test_txt.GetReader();
    string text = Content.TestAsset_Test_txt.ReadAllText();
    string textAsync = await Content.TestAsset_Test_txt.ReadAllTextAsync(CancellationToken.None);
    byte[] bytes = Content.TestAsset_Test_txt.ReadAllBytes();
    byte[] bytesAsync = await Content.TestAsset_Test_txt.ReadAllBytesAsync(CancellationToken.None);

• Via enum access through the Content[FolderName] enum:

    // Via the generated extension methods on the enum
    using Stream s = Content_TestAsset.Test_txt.GetStream();
    using StreamReader sr = Content_TestAsset.Test_txt.GetReader();
    string text = Content_TestAsset.Test_txt.ReadAllText();
    string textAsync = await Content_TestAsset.Test_txt.ReadAllTextAsync(CancellationToken.None);
    byte[] bytes = Content_TestAsset.Test_txt.ReadAllBytes();
    byte[] bytesAsync = await Content_TestAsset.Test_txt.ReadAllBytesAsync(CancellationToken.None);

NoneItemAccessGenerator

The Raffinert.NoneItemAccessGenerator is a code generator to allow easy access to all none item files with CopyToOutputDirectory attribute specified as Always or PreserveNewest.

Usage

Get the nuget package here.

After referencing the Raffinert.NoneItemAccessGenerator nuget the code generation will automatically create a class Nones in the root namespace of the project.

Together with the generated None enumeration there are several options to access none item files:

E.g. for a Test.txt none item in the TestAsset folder:

• Via enum access through the None enum:

    // Via the generated extension methods on the enum
    using Stream s = None.TestAsset_Test_txt.GetStream();
    using StreamReader sr = None.TestAsset_Test_txt.GetReader();
    string text = None.TestAsset_Test_txt.ReadAllText();
    string textAsync = await None.TestAsset_Test_txt.ReadAllTextAsync(CancellationToken.None);
    byte[] bytes = None.TestAsset_Test_txt.ReadAllBytes();
    byte[] bytesAsync = await None.TestAsset_Test_txt.ReadAllBytesAsync(CancellationToken.None);

• Via enum access through the None[FolderName] enum:

    // Via the generated extension methods on the enum
    using Stream s = None_TestAsset.Test_txt.GetStream();
    using StreamReader sr = None_TestAsset.Test_txt.GetReader();
    string text = None_TestAsset.Test_txt.ReadAllText();
    string textAsync = await None_TestAsset.Test_txt.ReadAllTextAsync(CancellationToken.None);
    byte[] bytes = None_TestAsset.Test_txt.ReadAllBytes();
    byte[] bytesAsync = await None_TestAsset.Test_txt.ReadAllBytesAsync(CancellationToken.None);

Motivation

Instead of using magic strings in the resource access code that may point to non-existant resources this generator guarantees resources to exist and code to not compile when they are removed.

Grouping the resources via their path adds path specific enums, e.g. to easily write tests for all embedded resource in a subfolder.

Also it saves quite a bit of typing effort.