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

packages folder no being installed with VS 2019 #1

Closed
komeilr opened this issue Jan 29, 2020 · 2 comments
Closed

packages folder no being installed with VS 2019 #1

komeilr opened this issue Jan 29, 2020 · 2 comments
Assignees

Comments

@komeilr
Copy link

komeilr commented Jan 29, 2020

Hi, I noticed the 'packages' folder doesn't get added when installing with NuGet on VS 2019.
I should mention Monogame templates don't work with vs2019 and I've had to use 'dotnet new mgdesktopgl' command to create project templates.

Luckily I have VS 2017 and just copied the packages folder from that. Just thought you might want to know

@manbeardgames manbeardgames self-assigned this Jan 29, 2020
@manbeardgames
Copy link
Collaborator

If you're dotnet new mgdesktopgl, this means you're using .NET Core. Technically, there should be no issue using MonoGame.Aseprite with a .NET Core project, however, MonoGame.Aseprite targets .NET Framework >= 4.6 to ensure compatibility with the main MonoGame release, which still at this moment only has VS2017 support officially without workarounds as you know.

If you're using .NET Core, the \packages\ directory is no longer placed into the root of the project folder. Instead, there is a global nuget directory at %USERPROFILE%\.nuget\packages\ on windows os.

So the full directory for the content pipeline reference dll should be

%USERPROFILE%\.nuget\packages\monogame.aseprite\1.1.1\content\

Let me know if this works for you and I'll get the documentation updated.

@manbeardgames
Copy link
Collaborator

Issue has been resolved with the recent update. Please see wiki documentation on how to add content pipeline references for monogame 3.8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants