· Jul 4, 2019

Options for .Net Managed Provider Proxy Classes in IRIS environment

Hi All,

I'm just taking a look at IRIS and what it has to offer, and if this is something the organisation I work for should be looking to take advantage of.

I think I've come across an early sticking point, and I wondered if anyone knew of any options.

The front end (.Net, mostly C#) codebase makes extensive use of the object binding through generated proxy classes, and I see that this option is omitted from the IRIS documentation (Cache: IRIS:

Do we take a hard pass on IRIS for the time being or am I missing something?

Thanks in advance.


Discussion (2)0
Log in or sign up to continue

Hi Alexander,

Thanks very much for that, looks like what we're after!

For any IS folks out there, I think there's a typo in the readme:-

'1) Remove references to InterSystems.Data.CacheClient.dll from the .NET project. Add references to InterSystem.Data.IRISClient.dll *and* InterSystem.Data.IRISClient.dll. If an application needs only ADO.NET features it can include only InterSystem.Data.IRISClient.dll but applications using Bindings features must include both dlls.'

I think the second reference to InterSystem.Data.IRISClient.dll should be InterSystem.Data.Bindings.dll?