Proposal: .NET Core

[alexellis]

This library appears to have some dependencies on "full" .NET 4.5.

Do you know what would it take to provide support for .NET Core / .NET Standard 2.0?

.NET Core / .NET Standard 2.0 runs well on Linux and Windows and can be developed with a smaller toolchain - i.e. VSCode.

[krmorse]

Love this idea. The .net toolkit has been around for 5 or 6 years, and the .net framework has come a long way since then. I can't remember what parts of it actually require the full .net, but I'm going to investigate creating a pared down version of this toolkit...

[krmorse]

@alexellis, So I did a quick spike on this and the results look promising. I'm using Json.NET for all the input/output, which is sweet because the json handling always felt clumsy in the existing library, and you can do sweet linq stuff on query results with that lib as well.

A couple questions:

• Do you need sso support?
• Anything else?

I'd love to just make a super lightweight lib with just the basics- crud + query, collection support, api key authentication, etc. - more inline with the other language toolkits.

[alexellis]

Wow thanks for getting back and for the spike. I think we just need oauth tokens right now. Linq is also very cool. I'm most excited about writing Rally functions on Linux with http://www.openfaas.com

I'll check on the other questions and get back tomorrow.

[JulieGarghan]

@krmorse awesome thanks for doing the spike. Where can I find this code please? I would really like to try out using this with .NET Core.

[krmorse]

@JulieGarghan, @alexellis here is what i have so far: https://github.com/krmorse/RallyRestApi.NETCore

It's pretty barebones at the moment, just basic auth, just GETS, no fancy config for proxies, etc, no parsing of results/errors/warnings. I'd love to collaborate on it if there is interest in the community. I haven't really figured out exactly how I want the API to look and feel- similar to the standard .NET toolkit, or something completely different.

[alexellis]

We would like to help you test this migration to .NET core. We do need proxy configuration box for connectivity though.

@JulieGarghan what are the absolute basic operations we'd need to do?

[krmorse]

If we just basically copied all the existing semantics over- Request/Response classes, api key support, proxy support, etc. that probably wouldn't take too long. I'm happy to give that a shot this week...

[JulieGarghan]

@krmorse wow that would be fantastic, thank you!

[alexellis]

Would this be a separate branch or a new repository? We'd ideally look to integrate via a NuGet package too, even if it's testing/alpha status initially.

[krmorse]

I'll probably leave it in my private repo for a little while. And yes, I'd intend to ship it as a nuget package for sure.

[alexellis]

Hi @krmorse - we're coming up for about a month since we last spoke. How is the .NET core port looking? We're keen to start using this and evaluating it for internal use.

Are there any roadblocks/unexpected issues?

Alex / @JulieGarghan

[krmorse]

Unfortunately I've had a bunch of things land on my plate the last few weeks and I really haven't had much time at all to dedicate to this...

[ferentchak]

@krmorse I didn't see this thread before. I spent a day trying to get this working on DotNetCore a few months ago . It's a total rats nest I think that since we used mainly methods from older version of .NET.

My guess is it is less work to remake this from scratch only keeping the tests.

[joseph19k]

Good Day Team,

Just wanted to check is there any update on this feature.

-J

[klehman-rally]

This feature is effectively stalled. krmorse has moved on to another position subsequent to the Broadcom acquisition of CA Technologies. Any work on this would have to be driven from the community or someone internal to Broadcom doing some hackathon work. Given the current priorities and resources it is very unlikely that this toolkit will get much TLC in the near future.