You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although it has part of the documentation, it is not complete because it does not address how one should do NBT file reads and reading tags from that file.
I also downloaded the ZIP, updated the compile to v4.8 but the solution fails to build. It always complains that the template (I suppose the T4 file) might be dangerous for my system. Having ignored that, the compilation fails with errors on the T4 file.
The text was updated successfully, but these errors were encountered:
Thanks for pointing that out, hadn't noticed I'd never added "how to read". I'll create a separate issue to avoid cluttering up this one.
You're going to need to provide some more context. There's a few T4 files in the library so you need to tell me what file(s) are failing and what the errors are. I just tried upgrading my local copy to 4.8 and executed "Transform All Templates" and VS was perfectly fine with it.
Although the library is currently targetted to .NET 3.5, if you add the package to a .NET 4.8 project it should work absolutely fine without you needing to compile your own version. Oh... oops. On checking why the NuGet link wasn't in the README either I remembered I'd published it to a private repo for some reason. Unexpected... I'll look at getting the package moved to NuGet.org this week. In the meantime, if you can clarify the errors you're experiencing as I'm unable to reproduce.
Although it has part of the documentation, it is not complete because it does not address how one should do NBT file reads and reading tags from that file.
I also downloaded the ZIP, updated the compile to v4.8 but the solution fails to build. It always complains that the template (I suppose the T4 file) might be dangerous for my system. Having ignored that, the compilation fails with errors on the T4 file.
The text was updated successfully, but these errors were encountered: