Hello, Most probably don't remember me but I used to co-author a C# library that provides an abstraction for the GW2 API. Unfortunately changes in my personal life stopped me from working on it about 5 years ago and the project became no longer maintained. If you check out the NuGet page you can see that the last update was in 2015. And that update was mostly just for bug-fixes... Rather than attempting to modernize an outdated library that's riddled with design issues (all my fault, of course) and outdated dependencies, I decided to take a fresh stab at it. I created a new Git repo and completely started over, using modern C# and .NET. This discussion exists for me to find out what people are doing these days: Are you currently using C#?Are you interested in using an API client library written in C#, for C#?Are you interested in collaborating on such a project?My design goals for the library: Provide an unopinionated API wrapper instead of an opinionated abstractionLet you retrieve data, add just enough type-checking to keep you warm and then get out of your wayFollow a test-driven approach to add features (documented here)Target .NET Standard 2.0 so you can use the library on a server, desktop, mobile or even an embedded deviceNon-goals (A.K.A. things I know you'll eventually need but I refuse to build them): Aggregating data, e.g. correlating recipes with items: you'll have to build this yourselfResilience with circuit breakers and automatic retries: there will be a tutorial on how to do this with PollyCustom timeouts: Polly can do this tooCaching: PollyOperational goals: Test code automatically Merge after it is code-reviewedPublish the library as a NuGet package in a continuous mannerKeep the lead time between API changes and package updates shortPowered by integration tests that compare real API data to static typesRun integration tests daily and notify collaborators whenever schema changes are detectedBuild trust between collaborators. Everyone gets to participate in both coding and reviewing code (accepting/rejecting pull requests). Respect people from all walks of life. Respect differences in knowledge levels. No code-shaming. Build trust with users by delivering high-quality, self-documenting code and delivering updates quicklyVision statement:I believe that software is not something you build once and then ship it off to users that you don't care about. Software is useless without users. Software needs to be operated like a machine. Code is vulnerable to wear and tear and can break in very similar ways if it isn't properly maintained. If you share this mindset, you understand that a project like this is a pretty big commitment that I can't take on alone. For this project to succeed, I'll need people who are interested in this stuff and who can support my vision with actions, for the benefit of the GW2 community. If this sounds like you, please let me know. Link: https://github.com/StevenLiekens/gw2sdk