Commit Graph

8 Commits

Author SHA1 Message Date
foxnne
7af4093e67 Fixed some issues with the powershell scripts inside of .vscode
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.
2019-09-04 01:14:21 -05:00
foxnne
3e5a7e6a78 Nearly finalized, added back all the osx compatibility.
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.
2019-09-02 17:49:21 -05:00
foxnne
7975cccbe9 Ported bash files to powershell, now functions in Windows
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)
2019-09-01 01:01:40 -05:00
Mike
b49cb32592 cleanse the magic Nez updater task 2019-02-20 00:18:17 -08:00
Mike
8c4c9d34ad new command to update Nez 2019-02-19 23:23:42 -08:00
Mike
2e933229b1 move to using Nez instead of Nez.FNA 2019-02-17 13:10:10 -08:00
Mike
ef9814253c switch to new ImGuiManager 2019-02-17 01:13:43 -08:00
Mike
d0572471ff push everything up one directory so vs code works more betters 2019-02-14 20:11:05 -08:00