World of Warcraft®

Following Cyaga's initial steps - I thought I'd contribute and build a C# library to access the Community Platform API.

I will continue to update the library as changes occur to the API and as we get access to other areas of the platform (characters,etc)

You can find the code at https://github.com/briandek/WowDotNetAPI

Please feel free to jump in and push changes where you see fit. Any feedback is more than welcome :)

This is something I'll more than likely contribute to when I get the time. First thing I notice, though, is the non-PascalCase public identifiers (as per Microsoft's guidelines for library developers http://msdn.microsoft.com/en-us/library/ms229042.aspx). I guess that'll be my first submission ;)

Briandek... that does ring a bell...
Aren't you that guy from TrinityCore (World of Warcraft emulator) trying to get packets with your illegal sniffers?
If you are, sorry, but you are retarded and I felt like saying this.
If not, then wrong person and have a nice day! >.<

*cracks fingers*

ps - test driven design for video game api? awesome.

Briandek... that does ring a bell...
Aren't you that guy from TrinityCore (World of Warcraft emulator) trying to get packets with your illegal sniffers?
If you are, sorry, but you are retarded and I felt like saying this.
If not, then wrong person and have a nice day! >.<

I think my nickname is pretty unique, but nope I'm not the person you're thinking of. Hope you have a nice day too :)

*cracks fingers*

ps - test driven design for video game api? awesome.

haha I should be mocking the tests, they're not really "unit tests", they're more like sanity tests if anything :P - I'll take some time over the weekend to clean that up as it's been bugging me for a bit.

Removed.

I'd thank you for the instruction, but telling me to use common sense is rude, considering the many times I've seen giant tracert dumps in your support forums along with dxdiag dumps.

I'll edit my post and remove the contents, and go back to lurking.

That's a completely different thing. dxdiag/tracerts are almost always pertinent for troubleshooting.

@Briandek: Had you considered a higher level abstraction around the whole thing? Given some relinq and dynamic proxy mojo it would be pretty easy. I was looking at writing a wrapper so you could write something like:

var servers = new[]{ "Thrall", "Cho'gall"}
using(var api = new Linq2Wow(ServerRegion.US))
{
var totalAchievementPointsForLevel85CharactersInGuildsStartingWithBobOnServers =
api.Servers.Where(s=>servers.Contains(s.Name))
.SelectMany(s=>s.Guilds.Where(g=>g.Name.StartsWith("Bob")))
.SelectMany(g=>g.Characters.Where(c=>c.Level == 85))
.Select(c=>c.AchievementPoints)
.Sum();
}


Let me know if you're interested.

Worth noting I shouldn't be worried about the absolute performance of these wrappers since (a) the bottleneck is going to be network and (b) you shouldn't be making so many requests.

That in mind, the above implementation as a C# wrapper would be super sexy. Minus that 74-character variable name. Also, I prefer full CamelCase in C#.

Briandek has kindly accepted my partnership offer in working on this C# Library
(tehmuffinman on GitHub)

Keep the suggestions coming!

Ferbmcgiggin's suggestion is definitely schmexy :)

1) I don't believe the posted code would need to preform an unreasonable number of requests. Given appropriate caching and query optimization it could be done in a number of requests equal to the number of realms + the total number of guilds starting with "bob". Remember the power of Linq lies in deferring execution until absolutely the last possible second.

2) While you might prefer camel cased member names they are most definitely outside the framework design guidelines see http://msdn.microsoft.com/en-us/library/ms229043.aspx. I for one don't want to be the corpse that inflicts a library with non-standard style on the world. I've used such libraries and the style differences are painful.

Brian and I forked the main branch to better facilitate co-development on this library.

For bleeding edge updates (experimental until they are pulled into the main branch) you can check out my fork here:

https://github.com/tehmufifnman/WowDotNetAPI

The master branch (https://github.com/briandek/WowDotNetAPI) has been updated!

See updated sample for new usage.

We are looking for feature suggestions from people who will use this library, so please post anything/everything that you would like to potentially see!

We look forward to seeing some awesome feature ideas. =)

Posting for Briandek as he can't atm:

"the library has been recently updated, you can access AH data now"

Briandek: "the library has been updated, now supports authentication and item data".

EDIT: Nothing to see here, move along. Asked a very long question that I was able to answer on my own and I can't seem to delete said post.

Is there anyone still active on this project? Haven't seen any action on the github site for about a month now, and I have some ideas on implementing some error handling for the different response codes that could come back. If so, please email me at james.p.mcconnell AT gmail DOT com. I'm also Github as interneth3ro. Thanks.