Closed AristurtleDev closed 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
%userprofile%\.nuget\packages\monogame-aseprite\5.0.0\lib\net6.0\MonoGame.Aseprite.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.
Resolved with 5.0.1 release #78
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 assemblyMonoGame.Aseprite
Steps to Reproduce
Open the mgcb-editor
Add the
MonoGame.Aserpite.Content.Pipeline.dll
reference to the mgcb-editor as documented here https://monogameaseprite.net/docs/getting-started/setup-mgcb-editorAdd an aseprite file as content
Choose any processor from the
MonoGame.Aserpite.Content.Pipeline.dll
referenceExpected Behavior
The content builds as expected
Actual Behavior
An exception is thrown stating that the
MonoGame.Aseprite
assembly could not be foundConfiguration
Other Information
No response