Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

monogame update #35

Closed
ghost opened this issue Jul 27, 2022 · 6 comments
Closed

monogame update #35

ghost opened this issue Jul 27, 2022 · 6 comments
Assignees
Labels
🐞 Bug A bug has been identified and need to be fixed.

Comments

@ghost
Copy link

ghost commented Jul 27, 2022

Hello

Monogame 3.8.1 is released recently.
Would it be possible to update monogame-aseprite so it works with 3.8.1?

Thank you

@ghost
Copy link

ghost commented Aug 7, 2022

I'm interested too to know if the current version should work in MonoGame 3.8.1 or if an update of monogame-aseprite is needed.
Is anybody working on this?

Thank you

@AristurtleDev AristurtleDev self-assigned this Aug 8, 2022
@AristurtleDev AristurtleDev added the 🐞 Bug A bug has been identified and need to be fixed. label Aug 8, 2022
@AristurtleDev
Copy link
Owner

@monogame-girl I apologize for the delay, I will try to have this updated within the next day or so. Some context below on why this isn't updated yet.

I have been working to get this library updated for a bit now to support Aseprite 1.3-beta, but that update is not quite ready. I mention this because starting with that update and moving forward, MonoGame.Aseprite will only be targeting the current .NET version (6.0 as of this comment).

I had not counted on MG releasing the 3.8.1 update which also moves forward with targeting .NET 6.0 and as I mentioned, the new MonoGame.Aseprite update isn't quite ready for production use yet.

In the meantime, I can update the current version to target the MG 3.8.1 packages and .NET 6.0. This is going to require a a lot of editing, as I can't just flip the <TargetFramework> value to .NET 6.0 and call it a day. I need to update all the code to support having <Nullable> enabled so there are no compiler warnings from that.

Again, I do apologize for the delay.

@ghost
Copy link

ghost commented Aug 8, 2022

Hi!

No problem! It's better to take your time and do it right then to hurry with a buggy release as result.
There is no hurry at all! I now use MG 3.8 until it's ready (and don't use .NET 6.0 features).

@ghost
Copy link

ghost commented Aug 8, 2022

Will all old releases for MG 3.8 still stay on nuget? That would be very usefull for people not using latest MG (for some reason).

@AristurtleDev
Copy link
Owner

Yes, older releases will remain on NuGet. I wouldn't remove them if possible, but this is actually a fundamental principle of NuGet. Unless there is some extenuating circumstance such as copyright violations NuGet does not allow the removal of old versions of a package when new versions are released.

Reference: https://docs.microsoft.com/en-us/nuget/nuget-org/policies/deleting-packages

@AristurtleDev
Copy link
Owner

Library has been hotfix updated to support MonoGame 3.8.1. See my explanation on twitter https://twitter.com/aristurtledev/status/1563232746360545281

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 Bug A bug has been identified and need to be fixed.
Projects
None yet
Development

No branches or pull requests

2 participants
@AristurtleDev and others