The dotnet-core-client repo is at best a placeholder at present, and is not suitable for any kind of use. It requires a special build of geode-native that contains c-style exported API functions, that is only available on a branch on one of my forks IIRC. It exists under the apache project because we desperately needed to get it under revision control to preserve WIP, and starting under apache avoided a potentially difficult future migration.
I can prioritize a PR to scrub proprietary names, but please understand we've been trying to get back to this repo for several _months_ now and been swamped with patch releases and customer bugs/support requests, so I don't wish to set expectations very high. As far as tests for the code, yes they exist and cover the "supported" API thus far, which is not a lot. If everything is set up correctly, however, creating a cache factory, cache, pool, region, and put/get of string key/value pairs works. Thanks, Blake -----Original Message----- From: John Hutchison <hutchiso...@vmware.com> Sent: Tuesday, December 29, 2020 11:24 AM To: dev@geode.apache.org Subject: Re: State of https://github.com/apache/geode-dotnet-core-client Is there some kind linting that we could put into spotless (or a linting tool that's run before spotless) to prevent this kind of thing (check against known proprietary names and derivatives before being allowed through ci)? From: Jacob Barrett <jabarr...@vmware.com> Date: Tuesday, December 29, 2020 at 1:08 PM To: dev@geode.apache.org <dev@geode.apache.org> Subject: Re: State of https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-dotnet-core-client&data=04%7C01%7Cbblake%40vmware.com%7C35d72397c8b5436f342808d8ac2f562e%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637448666604574411%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=alFiaIqSZZBmtPVHNYIzfHJBqJT6rthLXIPccs%2BwTGU%3D&reserved=0 Wow, that's pretty bad that we put proprietary references into this repo from the start. If you have the bandwidth a cleanup PR would be appreciated. I can't speak to the functionality but I would hope there are unit and integration tests that assert the supported behavior. -Jake > On Dec 21, 2020, at 4:48 PM, Michael Oleske <mole...@vmware.com> wrote: > > Hi Geode Dev Friends! > > I'm starting a personal little side project and was thinking of using Geode > as my backend (no real reason, certainly doesn't need the capabilities of > Geode, but thought it'd be fun.) I'm writing my application in .NET 5 (which > is core based) and was going to try and use > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-dotnet-core-client&data=04%7C01%7Cbblake%40vmware.com%7C35d72397c8b5436f342808d8ac2f562e%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637448666604574411%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=alFiaIqSZZBmtPVHNYIzfHJBqJT6rthLXIPccs%2BwTGU%3D&reserved=0 > > I see no one has really made any changes to it for a while, and that it seems > to have some proprietary references in it. Is it in a usable state for > simple puts/gets? > > -michael
