FYI Applications built on .Net Core worked with Geo SCADA 2019 but not newer versions

[geoffpatton]

We have a worked on a few applications built on .Net Core and one customer upgraded to Geo SCADA 2022 and their .Net 5 Core application could no longer connect to Geo SCADA but their .Net Framework 4.8 applications were still working. Ultimately they had to revert back to Geo SCADA 2019 May 2022 Update to get back up and running. It is an extensive program so a rewrite would not be a quick thing.

The Developers said Geo SCADA currently only officially supports .NET Framework 4.8 and had not tested any version of .NET (5 or 6) against Geo SCADA.  They also mention that they are surprised the .NET 5 application worked with Geo SCADA because of reports that .NET Framework and .NET do not coexist very well together in the same application. That being said they also were not aware of any changes in Geo SCADA that might have changed the connection behavior.

We did send them a small connection test application to test with but so far there is no indication that there will be a fix issued.

[sbeadle]

Thanks Geoff. The developers are looking in to this. Officially only .Net Framework 4.8 is supported by our ClearSCADA.Client.dll

Support by .Net 5/6/7 was unexpected - perhaps a new dll for those versions is the best way to go.

[_Experimentalist_]

Is there any news on support for .Net Core Steve? Is a compatible DLL in the pipeline?

[AndrewScott · Accepted solution]

This bug (CSUP-13435) has been fixed in the March 2024 releases of GSE 2022 (6.85.8853) and GSE 2023 (6.86.8863) onward, but was mistakenly missed from the release notes. The fix was tested with .NET Framework 4.8 and .NET 7.

[_Experimentalist_]

Hi Andrew

If I use the 6.85.8853 ClearScadaClient.dll in my import statement in PowerShell 7.4.1 core I can successfully  query my 84.8218.1 database on my development system.