We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello, do you have any plan to update this TCP Connector to .NET8
im trying to "Fix" this issue on .NET8 but can't complete, i try with Protobuf to Serialize and Deserialize messages.
Type is not expected, and no contract can be inferred: Scs.Framework.Communication.ScsServices.Communication.Messages.ScsRemoteInvokeMessage
The text was updated successfully, but these errors were encountered:
To "Add" support for .NET8 this is a Trick
Add into your .csproj and Scs.dll .csproj this line
true
This is my ScsNet8.csproj
<Project Sdk="Microsoft.NET.Sdk"> <PropertyGroup> <TargetFramework>net8.0</TargetFramework> <ImplicitUsings>enable</ImplicitUsings> <Nullable>enable</Nullable> <EnableUnsafeBinaryFormatterSerialization>true</EnableUnsafeBinaryFormatterSerialization> <AssemblyName>Scs</AssemblyName> <RootNamespace>Hik</RootNamespace> </PropertyGroup> <ItemGroup> <PackageReference Include="protobuf-net" Version="3.2.30" /> </ItemGroup> </Project>
Sorry, something went wrong.
No branches or pull requests
Hello, do you have any plan to update this TCP Connector to .NET8
im trying to "Fix" this issue on .NET8 but can't complete, i try with Protobuf to Serialize and Deserialize messages.
Type is not expected, and no contract can be inferred: Scs.Framework.Communication.ScsServices.Communication.Messages.ScsRemoteInvokeMessage
The text was updated successfully, but these errors were encountered: