[Solved] The .Net Framing mode being used is not supported
Introduction
Here we will see how to fix the exception, the .Net Framing mode being used is not supported by ‘net.tcp://….’ See the server logs for more details.
How to fix this exception
The .Net Framing mode being used is not supported by ‘net.tcp://….’ See the server logs for more details. This exception occurs when we change the TransferMode of tcp communication either at service side or client side to Streamed and the other side still uses the default mode which is Buffered.
The TCP three way handshake protocols use a Framing mode to transfer packets by default. When we change this behaviour, we have to make sure that the communication happens properly between client and server. If you use Streamed mode then the system expects the communication happens to and fro from service as streamed. If you are not indented to use so and you want only client to stream message and server to behave default then you can use TransferMode.StreamedRequest or TransferMode.StreamedResponse.
I am currently working as a lead engineer in one of the leading wind turbine manufacturing firm. I have wide range of interests and getting my hands dirty in technology is one among them. I use this platform primarily as my knowledge base. I also use this platform to share my experience and experiments so that it might help someone who is walking the way I already did. The suggestions expressed here are the best to my knowledge at the time of writing and this may not necessarily be the best possible solution. I would pretty much appreciate if you could comment on it to bring into my notice on what could have been done better.