I'm trying to run a .NET 4.6.1 with RTI 6.1.1.
I keep getting error related to nddsc.dll - is this dll should be included in the running environment ?
I'm trying to run a .NET 4.6.1 with RTI 6.1.1.
I keep getting error related to nddsc.dll - is this dll should be included in the running environment ?
Dear Community,
I'm trying to use the request reply pattern in net5 under Linux (Debian 11 x64).
I see in the User Manual (Part4 Chapter 27) how they supposed to work, and I found cpp examples.
I also found a forum topic explaining the usage for dotnet framwork 4.5 (a dll reference is required from %programfiles%\...), but I can't seem to find neither the Requester nor the Replyer types for .net5.
Can you please help me how to use the request-reply pattern with .net5 (netcore) from under Linux (and possibly from under Windows too).
Thank you!
As Microsoft begin move .NET Framework to .NET Core and .NET Standard since 2015, our company will follow official suggestions to start take move with the Environment and starting using .NET Core and .NET Standard as side project first. We would want to know,
1) Does NDDS 3.X support it? If yes, could you please provide related documentation for how to build up the environment?
2) Does NDDS have any plan to porting to .NET Core or .NET Standard before 2018-2019? If no related plan yet, please response to let we know. Thanks!
Reading the documentation for Extensible Types, it says that optional members are not supported in the .NET API. What exactly is the resulting behaviour of this? For instance, what happens if a Java application publishes a sample where some optional members are not set and a .NET application is subscribed to that topic? Will it result in a crash? Will the .NET application get null values for the unset fields? Will the publisher/subscriber simply not match?
I am using the C# .Net API for RTI Community DDS.
I am trying to query DDS on demand using a QueryCondition and read_w_condition() on a typed DataReader. I am trying to use the DataReader to access or take data I have previously published on demand from the application so that I can use DDS as a store of data. I am using multiple threads as I am servicing multiple interfaces.