Change from gRPC to Named Pipes

[RandallFlagg]

Today there is a need to install asp.net core in addition to .net core because of gRPC.
Also, inorder to communicate in a faster and better way between proccesses(IPC) of LogExpert we will change the communication from gPRC to Named Pipes.
gPRC will be used probably in a differnt part of the code(e.g. source of log) but not for the IPC purpose.

The reason choosing this was .net core support and cross platform.

[Hirogen]

What is the USE CASE for InterProcess communications, why would I want to communicate between logexpert processes, is this really necessary?

[RandallFlagg]

What is the USE CASE for InterProcess communications, why would I want to communicate between logexpert processes, is this really necessary?

Same question I was asking my self from the begining. Since you are the project lead and owner I though you knew. :)
Luckaliy we have the code to answer your question.

LogExpert/src/LogexpertgRPCService/Protos/Logexpert.proto

Lines 10 to 20 in 8fba5b8

	service LogExpertService
	{
	// Sends a log message
	rpc SendLog (LogRequest) returns (LogReply) ;
	rpc LoadFiles (FileNames) returns (FilesReply);
	rpc NewWindow (FileNames) returns (FilesReply);
	rpc NewWindowOrLockedWindow (FileNames) returns (FilesReply);
	//is this really needed?
	rpc WindowClosed(google.protobuf.Empty) returns (google.protobuf.Empty);
	rpc GetLogWindowCount(google.protobuf.Empty) returns (Count);
	}

[Hirogen]

yeah I implemented that, because that was in the old code, but I could never find a real use case where to use that.

[RandallFlagg]

Maybe let's open it for discussion so people can say what they need from a multiple window/instance of LogExpert. The only one I can think of is to move tabs between windows.