-
With version 4.1.0.
I am using an `IceRpc::ServiceAddress`. The code compiles fine but the Language Server is not happy:
```
[{
"resource": "/C:/Users/bernard/source/repos/icerpc-ice-csharp-i…
-
The behavior of slicec-cs seems at odds with the behavior of the IceRpc.Slice.Tools:
when there is a Slice file, Slice.Tools adds the corresponding .cs file to the C# compilation. However, slicec-c…
-
We should fix all text files to use LF line endings as per:
https://code.visualstudio.com/docs/remote/troubleshooting#_resolving-git-line-ending-issues-in-wsl-resulting-in-many-modified-files
Wi…
-
This generated file is currently the only Protobuf service tests and shows some bugs:
```csharp
public partial interface IMyWidget
{
-
I am getting the following build failures when building [icerpc-ice-csharp-interop](https://github.com/icerpc/icerpc-ice-csharp-interop) with .NET 8 RC1:
```
C:\Users\bernard\source\repos\icerpc-i…
-
The ideal however would be to refactor the code to encode proxies as their "value.ServiceAddress" and use the regular ServiceAddress encoding (as provided by the custom ServiceAddress type). Not dupli…
-
### Description
For collection types, we need to generate EncodeAction functions, and the implementation of this function depends on whether the collection is of value or reference types.
For cu…
-
Getting started should included a short intro to Slice vs Protobuf since the reader will need to pick one over the other.
-
Should be just like slice and csharp, e.g.
```protobuf
syntax = "proto3";
package visitor_center;
option csharp_namespace = "VisitorCenter";
// The protobuf equivalent of Slice interface Gr…
-
https://docs.icerpc.dev/slice1/language-guide/class-types#slicing
Should automatically jump down to the 'slicing' section of the class page, but instead it stays at the top of the page.
This happens…