-
Notifications
You must be signed in to change notification settings - Fork 192
Does not work on netcoreapp2.1 #121
Comments
Hey, I'm also using net core 2.1 and C# and it seems to be working as expected for me using (var client = new ConsulClient(opt => { opt.Address = new Uri("http://localhost:32822");}))
{
var result = await client.KV.Get("database/connectionstrings/
} Im not sure about F# never used, but i know it does work on .net core 2.1, sorry i couldnt be of more assitance |
I have same problem in C# as well ..
ends up with
The code, url, prefix and everything is same I just change from So @johnfg10 are you really sure that it works for you? Because I have some result but there is an invalid response in it. |
Mayby try using |
It doesn't really matter which method I use. Both of them works fine on |
Ok so I've tested further it 100% works for me maybe its a mac issue because of this code: public async void test()
{
Console.WriteLine("test start");
using (var client = new ConsulClient(opt => { opt.Address = new Uri("http://localhost:8500");}))
{
var result = await client.KV.List("test");
foreach (var kvPair in result.Response)
{
Console.WriteLine(kvPair.Key);
Console.WriteLine(Encoding.UTF8.GetString(kvPair.Value));
}
}
Console.WriteLine("test end");
} prints this in console
which is the values in my consul key store. I have attached the test app I made so you can test, but I know 100% it's working for me on windows |
Hello,
I'm trying to implement a simple app to read values from
consul.KV
.I've made an example app in F# using you library. Code is here: https://github.com/MortalFlesh/fsharp-consul
It works fine, when I'm using
netcoreapp2.0
.But when I change
netcoreapp2.0
tonetcoreapp2.1
it does not work..<null-response>
is a fallback whenclient.KV.Get(key).Result.Response
isnull
I'm running the code on
Mac OS High Sierra 10.13.6
withI have a problem with
client.KV.List()
as well, but I wanted to simplify this as much as possible.Do you know what might be the problem? Am I doing something wrong?
Thanks for you reply.
The text was updated successfully, but these errors were encountered: