Posted by: twice2double
« on: May 10, 2021, 10:52:05 PM »There shouldn't be a dependency on the NewtonSoft library when you're developing a patch, only the main AuroraPatch project itself has that dependency. Not requiring patch creators to pull in that dependency is the whole reason it is abstracted away behind the Patch.Serialize and Patch.Deserialize methods. There should be no reason to pull in the entire AuroraPatch project (or any patch dependencies) to develop a patch. Just take the AuroraPatch.exe file and include a reference to it, the same should be possible with any patch's .dll file when you want to use it as a dependency. Just make sure, when you release your patch, not to include those files in the output.
Yeah the NewtonSoft dependency isn't needed on the patch itself but I felt the need to include the other projects because microsoft studio kept complaining about the project not loading correctly since the T2DTheme was looking for them regardless.
This is my bad - I hooked it up locally so that everything is referencing the project files so AuroraPatch, ThemeCreator, and T2DTheme all get compiled if anything changes. It made my life a bit easier as I was making changes to all three projects at one point.
I'll fix it soon so it references the binaries like 0's and 1's said.