Geek Answers Handbook

WCF and NetNamedPipeBinding - AVG Antivirus

We have some customers receiving a warning from AVG Antivirus about our application.

Our application opens the standard NetNamedPipeBinding with WCF in C #, only for interprocess communication.

Is this something we can somehow solve? I am wondering if there is anything we need to indicate that the WCF service is local to the machine only.

Right now, we just set the binding in C # as follows:

var binding = new NetNamedPipeBinding(); binding.MaxReceivedMessageSize = int.MaxValue; binding.MaxReceivedMessageSize = int.MaxValue; binding.ReaderQuotas = XmlDictionaryReaderQuotas.Max; binding.ReceiveTimeout = TimeSpan.MaxValue;

I do not see other important settings, we just call ServiceHost.AddServiceEndpoint with an address like net.pipe: // localhost / OurEndpoint to establish the binding.

I would like to tell our customers that AVG is a piece of junk - they would be better off putting a rabbit's foot in their floppy drive, but my conscience will not let me.

+4
source share
2 answers

We never solved this problem, but adhered to WCF.

We did not encounter other client machines with this problem.

0
source

This is a bit more complicated than using WCF, but you can just use TcpClient and TcpListener (in System.Net.Sockets), which can be used to open a real TCP port and exchange data (make sure to listen to IPAddress.Loopback, not Any , or you may receive a firewall warning). It is cross-platform (Mono and .NET) and seems to work normally!

0
source

More articles:


All Articles