Skip to content

Fixed a few windows issues, make Monogame optional without requiring .csproj edits#4

Open
foxnne wants to merge 12 commits intoprime31:masterfrom
foxnne:master
Open

Fixed a few windows issues, make Monogame optional without requiring .csproj edits#4
foxnne wants to merge 12 commits intoprime31:masterfrom
foxnne:master

Conversation

@foxnne
Copy link
Copy Markdown

@foxnne foxnne commented Sep 22, 2019

  • Fixed Build and Run (Debug) and Build and Run (Release) vscode tasks for Windows
  • Modified MonoGameContent.targets to check for monogame being installed before running buildcontent after the build target, hopefully makes monogame optional without requiring editing of the csproj file. Tested fine on Windows with and without MG.
  • Removed exit from dotnet check in getFNA.ps1, shouldnt exit if you don't want t4 templates or have dotnet installed now, matching original getFNA.sh
  • moved nez-logo-black.png to the Content/Textures folder and switched load method in DefaultScene.cs to look for it there

Still need to fix up a few lingering things. Need to figure out how the original sln file was functioning with Release configuration without having a Release config set up. Would also be nice to have some way to install and run the powershell script from code, so it would be as simple as creating the folder for the new project > right click > open with Code > (run command from pallette for new Nez project from template)
Hopefully this now works with both OSX and Windows... I tried to create platform specific properties everywhere I could. All Windows build tasks for VSCode seem to be working correctly now.
Accidentally left in a testing name...
I had only tested the other configuration on a single project and in practice saw that the current vscode terminal location would cause a fail if it was in use. Now the build task uses a reference location...

Also fixed a few of the build tasks which seemed to work before, but werent calling anymore for some reason using the & modifier. Now thye seem to always work using the powershell command to open the ps1 files.
Hopefully now have all the camelCases covered...
@JacobMillward
Copy link
Copy Markdown

@prime31 @foxnne What's happening with this PR? Some of the additions look very useful.

@foxnne
Copy link
Copy Markdown
Author

foxnne commented May 11, 2020

It's been a while, when I started with this I had issues on windows with the shell scripts and added a few changes I thought fit in. But I think prime has already ironed out windows issues without this PR? Probably should just be closed.

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

Successfully merging this pull request may close these issues.

2 participants