EVE Technology Lab

I've decided to release the C# library I wrote for accessing the public eve API.

While there are other .net libraries out there, none that I know of both support all of the API calls, and include the full source.

EVE.Net supports all current API calls, including the image server, contains the full C# source code and is released under the MIT library. Modify/use as you see fit.

You can download the latest release from here.


The project is written in Visual Studio 2010. You will need some version of that to compile it, though converting it to 2005 or 2008 should be trivial. The library is compiled against .NET 2.0, so it should be mono compatible, though I have not tested that.

The only API calls I could not test are the ones that deal with sovereignty and outposts. If any 0.0 corp directors get a chance to test those calls, I would appreciate it if you would let me know if they work or not.

Example use:

CharacterSheet charSheet = new CharacterSheet(keyID, vCode, charID);
charSheet.Query();

Console.WriteLine(" Name: {0}", charSheet.name);
Console.WriteLine(" ID: {0}", charSheet.characterID);
Console.WriteLine(" Date of Birth: {0}", charSheet.DoB);
Console.WriteLine(" Race: {0}", charSheet.race);
Console.WriteLine(" Bloodline: {0}", charSheet.bloodLine);


Email me with any problems you may have.

Change History

1.0 06/03/2012
Initial Release

1.1 06/24/2012
Fix for non-english unit conversion. (commas instead of decimal points, etc).

1.2 07/05/2012
Added a prefix to all cache files for api calls made against the test server.
Added a fix for unexpected 'bool.parse' method suddenly missing.
Removed the trailing '\' character from the EVEConstants.eveServerStatusUri string that was causing issues with determining the cache file name.
License changed from Boost license to MIT license (to satisfy Goole Code)
Added a try/catch around APIReader:Query for WebExceptions.

1.2.1 07/19/2012
The format of cache file names has been changed. Rather than including the entire argument line in the filename, the argument list is now encoded as an MD5 hash.
This resolves an issue where certain API calls could generate cache file names that exceeded the OS filename length limits.

Now caching the return of 'IsCorpKey' to reduce the number of unnecessary web requests.

1.2.2 08/20/2012
Adjusted 'roleID' in CharacterSheet.Role to be an Int64, per a post by Virppi Jouhinen (from the 'Elinor' project) where she indicated an out of range exception.

1.2.3 08/24/2012
Updated AccessMask to uint32
Fixed an incorrect xpath issue that was causing nested objects to not read correctly (ie: AttributeEnhancers in CharacterSheet)

that's because he's using reflection to map an xml attribute to the object property. You could use the same method by declaring a custom attribute on object properties so you can respect CamelCase.

Good work otherwise, even if reflection is damn slow.

All the API are read only so you could expose interfaces instead of classes and keep your implementation private. It would solve the problem without rewriting everything.

Can you double-check this Takahiro? I am not able to reproduce the problem.

Xml output

Test result

@Cuhlen
Try applying CA (Code Analysis) rules for Globalization in your project. http://msdn.microsoft.com/en-us/library/dd264912
Overall it's a good practice to CA any project.

An update has been posted which should resolve the issue.

Thanks for the help guys.

Just an update...

As I mentioned, I had considered adding a data access layer to the API. However, I would prefer to leave the EVE.Net api small and focused.

That said, I am in the process of writing an additional library which provides data access to the static database dump provided by CCP. Currently, I have the library accessing the database, and have written some basic accessor methods, such as:

public DataTable GetDataTable(string sql_query, params object[] args)

While developing all of this, I wrote a test application which I'm considering releasing as well, (with some cleanup, it would make a decent EVE application development environment). Here are some screenshots...

api test
manage accounts
sql query
docking

The sql query view has syntax highlighting for SQL and for the data tables and columns. I am still toying with the idea of adding intellisence to the editor, but that will likely be down the road a bit.

I've still got plenty of work to do on the data access layer, as I want to provide methods to convert EVE.Net results to data that is more usable in a UI. The test application is written in C# using WPF, so I will probably have the data access layer convert api results to view models that WPF can work with.

The only real gotcha to this data access layer is the size. The test application installer is nearly 80 megs, and uncompresses to around 400mb, nearly all of that is the sqlite database itself.

Update posted that resolves an issue with cache file names being too long in certain cases. (very long argument strings for api requests).

In a nutshell, yes.

The zip file contains a visual studio project file 'Eve.Net.csproj' that you can add to your Visual Studio solution. You will need to essentially;

(In Visual Studio)
Create a solution for your project. This will create a solution file and a project file for your project.
In the solution explorer, 'add|existing', browse to the eve.net project file you downloaded and add that.
In your solution, you should now have both projects. Under your new one, right click and select 'add reference', select the 'projects' tab and select Eve.Net

You should now be able to use the eve.net library in your project.

Alternately, at the eve.net project wiki you can download the entire source project which includes an 'AppTemplate' visual studio solution which I use to test Eve.Net - you can use that as a starting point for your own project. There are instructions on the wiki page (under the 'Source' option) for downloading the code that way.

That's a pretty significant difference. I can only guess that you must get alot more functionality. If all you need though is direct API access (no database information), then yeah, Eve.Net is pretty lightweight. For me though, the argument always came back to the source code. I just don't like using libraries that I don't have the source to.