search

Drake53 / War3Api

Warcraft III's Common and Blizzard API's in C#.
MIT License
23 stars 4 forks source link

Issues using War3Api.Object to read a 1.32 map #15

Closed YakaryBovine closed 2 years ago

YakaryBovine commented 2 years ago

I can't use War3Api.Object from NuGet because that version only contains UnitType enums present in Warcraft 3 1.31. Right now I have to generate War3Api.Object using my own object data, but I'd really like to use NuGet if possible. Do you have any recommendations? Perhaps I could provide you with my Warcraft 3 object data so that you can generate the appropriate enum files? Alternatively I could fork that particular project and make a forked NuGet package.

Drake53 commented 2 years ago

Easiest solution for now would be to create a local folder package source, then build it yourself and put the package there. In visual studio: Tools > Options > NuGet Package Manager > Package Sources

The issue I have with 1.32 (applies to War3Api as well) is that if I put all versions in the same package, then visual studio will nag about not having the latest version, even though I'm intentionally staying on 1.31, and if you put them in different packages (like I did with War3Api.Legacy) and you try to use a library that relies on the 1.32 version, you get build errors, which can only be fixed by using different namespaces for each package.