AristurtleDev / monogame-aseprite

A Cross Platform C# Library That Adds Support For Aseprite Files in MonoGame Projects.
https://monogameaseprite.net
MIT License
163 stars 14 forks source link

Error when building content. Pipeline needs reference to MonoGame.Aserpite assembly #76

Closed AristurtleDev closed 1 year ago

AristurtleDev commented 1 year ago

Description

When attempting to build any content using the MonoGame.Aseprite.Content.Pipeline.dll reference in the mgcb-editor, an exception is thrown stating that it has no reference to the assembly MonoGame.Aseprite

Steps to Reproduce

  1. Create new monogame project, type doesn't matter, scenario below uses desktop gl
mkdir ./example
cd ./example
dotnet new sln -n Example
dotnet new mgdesktopgl -n Example
dotnet sln add ./Example
cd ./Example
dotnet add package MonoGame.Aseprite --version 5.0.0
dotnet restore
  1. Open the mgcb-editor

    # from within the project directory
    dotnet mgcb-editor ./Content/Content.mgcb
  2. Add the MonoGame.Aserpite.Content.Pipeline.dll reference to the mgcb-editor as documented here https://monogameaseprite.net/docs/getting-started/setup-mgcb-editor

  3. Add an aseprite file as content

  4. Choose any processor from the MonoGame.Aserpite.Content.Pipeline.dll reference

Expected Behavior

The content builds as expected

Actual Behavior

An exception is thrown stating that the MonoGame.Aseprite assembly could not be found

Configuration

Other Information

No response

AristurtleDev commented 1 year ago

Issue is caused by most recent version update where new processors were added to the content pipeline.

Pipeline now references the main library assembly.

For now, users can resolve this by adding the main library assembly as a reference as well. To do this, follow the same steps as when adding the pipeline dll, only this time add the following dll

⚠️ The above file paths assume default global nuget package directory. If you are using a nuget.config to download packages local to the project directory, you'll need to adjust the path to that directory instead.

AristurtleDev commented 1 year ago

Resolved with 5.0.1 release #78