Skip to content

discussions Search Results · repo:icerpc/icerpc-csharp language:Dockerfile

Filter by

16 results
 (66 ms)

16 results

inicerpc/icerpc-csharp (press backspace or delete to remove)

icerpc/icerpc-csharp
: 
I want use ice storm , but i do not know how

I reviewed the doc times by times, still do not have a clue. How can I start the storm service? On windows, with c#.Tools that downloaded never worked.May be the doc can have more details in the future, ...

icerpc/icerpc-csharp
: 
IceRPC 0.4 adds support for .NET 9.0

We are delighted to announce the release of IceRPC 0.4.0 for C#! This new release supports both .NET 8.0 and .NET 9.0 RC1. Microsoft made significant improvements to QUIC in .NET 9.0, and we recommend ...

icerpc/icerpc-csharp
: 
Can I use this library In Unity ?

icerpc/icerpc-csharp
: 
WASM Support?

Desired feature I don t see a place to ask questions so unfortunately I am placing it here. Does this project work with WASM? Specifically Microsoft Blazor. Problem No response Alternatives No response ...

icerpc/icerpc-csharp
: 
Server -> Client Invocations

With the existing API documentation and examples I was able to write a few successful test applications of Client - Server invocations and responses. However, I d like to support Server-originated messages ...

icerpc/icerpc-csharp
: 
Add F# support

Since you have just added discriminative unions and Result type (Which is most probably for Rust convention compatibility), You can add F# which natively supports both types.

icerpc/icerpc-csharp
: 
Implement a feature for fallback from one protocol to another

Since QUIC works on UDP, we may have problems using some Internet Service Providers. If we can use a feature which allows us to provide a list of protocols by priority, it would be great! For example: ...

icerpc/icerpc-csharp
: 
IceRPC 0.3 adds Discriminated Unions and Result to Slice

We are delighted to announce the release of IceRPC 0.3.0 for C#! This release refines the Slice language with the addition of discriminated unions and the new Result Success, Failure type. Give it a try ...

icerpc/icerpc-csharp
: 
How can I send error details to the client?

We are using Redis for invocation: In the client side, we have implemented IInvoker and put the OutgoingRequest into Redis stream, and the server reads the IncomingRequest from Redis stream and uses DispatchAsync ...

icerpc/icerpc-csharp
: 
Can we use inline comments within slice files and expect inline comments in generated C# code?

Some IDL languages has the capability of inline comments, and the generator copies the comments in place of the generated function code. Can we have the same feature here?