EVE Technology Lab

EveLib is a .NET Library for the Eve Online API, CREST and other popular APIs. It is written in C#, is open source and licensed under Apache v2.

EveAuth Utility: A small CLI tool to assist in obtaining access- and refresh tokens for the Eve SSO service.
https://forums.eveonline.com/default.aspx?g=posts&t=480927

All In One: (except DynamicCrest)
https://www.nuget.org/packages/eZet.EveLib

Single Packages:
https://www.nuget.org/packages/eZet.EveLib.DynamicCrest/
https://www.nuget.org/packages/eZet.EveLib.EveAuth/
https://www.nuget.org/packages/eZet.EveLib.EveXml/
https://www.nuget.org/packages/eZet.EveLib.EveCentral/
https://www.nuget.org/packages/eZet.EveLib.EveMarketData/
https://www.nuget.org/packages/eZet.EveLib.Element43/
https://www.nuget.org/packages/eZet.EveLib.ZKillboard/
https://www.nuget.org/packages/eZet.EveLib.EveWho/
https://www.nuget.org/packages/eZet.EveLib.StaticData/
https://www.nuget.org/packages/eZet.EveLib.EveCrest/ [Discontinued]
Wiki: https://github.com/ezet/evelib/wiki
Source: https://github.com/ezet/evelib
Symbols: http://nuget.smbsrc.net/

Supported APIs

• Eve Online API
• Eve Online CREST
• Eve Central
• Eve Market Data
• Element43
• ZKillboard
• EveWho
• Eve Static Data (Element43) [partial]

Features

• Fully asynchronous using TAP
• Thread safe
• XML configuration through app.config.
• Access to all popular APIs through one library.
• Provides caching for CCP API requests.
• Modular and open source; you can easily change the caching, serialization or any other part of the library.
• A fairly comprehensive set of unit tests, including static xml samples for calls requiring authentication.

For more information, downloads and examples, visit the Github repository.
You can also contact me on IRC, I'm on Coldfront in the official #eve-dev channel as "eZet".

Release notes:
https://github.com/ezet/evelib/releases

Updated again with some more bugfixes. Added a better way to check if a given key is valid, and implemented support for parts of the api provided by element43. Next on the schedule is a few more of the calls to element43 and then the CREST api.

Heya, nice work there! Just took a quick look at your code, did you know that you have to take the current culture settings the program is running under into account when you are parsing numbers? I can't see any use of cultures in your code, but as said, I just skimmed it.

When parsing the security status for example I have to do

var culture = new CultureInfo("en-US");
c.SecurityStatus = float.Parse(cResult.Element("securityStatus").Value, culture);

to parse this correctly: -2.66483930517884

That's because the point is used to group thousands in Germany, the colon marks the decimal part. Just wanted to tell you that, if you are already aware of it never mind me!

Greetings,
Jack

Edit: Actually you are using CultureInfo.InvariantCulture to parse Decimals, all good! ;)

Sorry for the late replies, I was sure I had added notifications for this topic, but it doesn't seem to be working.

About parsing decimals, I believe it should be working, but if there are any bugs let me know and I'll fix it asap.

About the caching, every page is cached locally by Windows, assuming you are running that. I'm not entirely sure how it works under other OS, feel free to provide some feedback. So unless you clear the IE cache, the returned data is available there and is used by the library on subsequent requests. The caching part was written very quickly, and isn't very robust. I will implement a custom cache in the near future.

If you however want to write your own, you simply need to implement the IRequestHandler for complete control, or use CachedRequestHandler which already implements IRequestHandler with some default logic for caching.

Again, I'm really sorry for the late replies, I simply haven't checked this for a while assuming I would get notified. Bugs and other requests are normally responded to within a day.

Found a bug in the update, app crashes in the Store() function, namely the "File.WriteAllText(Config.CachePath + Path.DirectorySeparatorChar + GetUriHash(uri), data);" line. It's because the directory is not created anywhere in the app, and I assume that when you ran it yourself, you already had that path.

Basic CREST support has been added using dynamics. All current endpoints should be working. Not sure if I want to spend too much time on it in it's current state as things may likely change still. But if there are requests for it, I can add more robust handling for the current CREST endpoints.

Also added a UserAgent option in App.config, as CCP wants you to use your applications name when requesting data.

I do not participate in PI, making it hard to test these endpoints. Would someone be willing to share an API key for a PI characters for an hour ? You can delete the key afterwards, or if you're willing to leave it enabled I can write some tests as well. Just send me a PM with the key if you're willing to help out

Is this thread safe? I've used another library for a while and found much to my annoyance that is isn't.

After giving it some thought, I can think of a few things that aren't thread safe, but these are mostly minor issues that I can probably have fixed tomorrow. If you would like to use it in a threaded environment and provide me with bug reports I'm sure we can get rid of them pretty fast.

As for journals: you can't get them past a certain date (1 month), but you certianly can retrieve them as often as you like during that period.

Same's true for assets. What you miss ofc is the change of assets in between two cache calls:

- pull API the first time, caching starts
- add item A to your assets
- remove item A from your assets
- caching expires, pull API a second time


From an asset API POV, item A has never existed.