teebeast

I've tested it shortly with my project, but it's not running. The problem with newer versions than 5.0.5 was, that the LS_CID has changed and was not accepted from server anymore. So I think that IG uses an older version of Lightstream Server. The LS_CID seems to be used to keep compatibility between client library and server. Here my log:

Windows 7 (and 8.1 in January 2023) is out of support by Microsoft. As a developer I recommend you to keep your os, your development tools and used framework up to date. At least at offical supported versions.

@charlie303 You cannot update lightstreamer .net standard client higher than 5.0.5, because they changed some things that are not compatible with the server version IG is using. Here is the changeset at Github which shows you the incompatible change. I got the latest version of Lightstreamer-lib-client-dotnet to run, when I change the parameter LS_cid which I cannot recommend. I also looked at the chart data with my demo account and has no problems. A problem could be the demo app itself. I only reworked the parts that were necessary to obviously run against the latest nuget packages. Maybe there are some bugs which I cannot reproduce.

@charlie303 I just tested CS.D.AUDUSD.MINI.IP with my own implementation and I got values. Generally its the same implementation but i try to give it a cleaner structure of code. So it should also work with IG sample app.

@charlie303 When I fixed it, I had no problem with refreshing values. When you create a test project at Github, I can look at your code. I implemented my own sample api including lightstreamer and its working fine. But currently I cannot publish it to Github, because I have to do some refactorings and removing secure information from source code.

@swingwin I fixed it short before i wrote my post. So please try it again.

Hi, I looked at my fork and found a bug, that the GET request /session?fetchSessionTokens=true was not called. So there was no correct authentication against lightstreamer. The sample application now works with my demo account. Thanks to thompsont1962 at Github. For more information see https://github.com/teebeast/ig-webapi-dotnet-sample.

Hi Charlie, try to create a new API-Key for DEMO access. It seems that the Lightstream server has its own blocklist, independant from the REST server. Maybe this is a problem in your implementation. Or is a result of heavy debugging and testing.

Which version of LightStreamer .NET library do you use? I tested the NuGet-Package Lightstreamer.DotNetStandard.Client version 5.0.5 and I had no problems with my demo account. Do not use any newer version because its not compatible with IG.

The use of DotNetClient_N2.dll is the problem. It seems to be outdated and there is a new implementation of it at GitHub. The example implementation has the same problem for a few weeks. IG - C# Example project at GitHub I fixed the C# example in my fork so you can see what to change. Hope it helps. Fork - Fixed Implementation for Lightstreamer (Changeset)

I am implementing an own version of this api in C# and tried to use the latest version of lightstreamer (5.1 and above). They changed something that wont work anymore in combination with IG. I had to use version 5.0.5 or earlier. https://github.com/Lightstreamer/Lightstreamer-lib-client-dotnet I only tested it with my demo account today and it works fine. When they upgrade to the latest lightstream server than this could be a problem. I will try it later for my live account.

I fixed this issue in my Fork and reworked some things that where outdated. Look at this Issue #12 and Issue #18 for more information about the changes in my fork. I asked if I should pull request my work, but i got no answer.