Skip to content
New issue

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

getting Pipe is broken exception when running on Windows 7 #20

Open
wdstest opened this issue May 17, 2019 · 1 comment
Open

getting Pipe is broken exception when running on Windows 7 #20

wdstest opened this issue May 17, 2019 · 1 comment

Comments

@wdstest
Copy link

wdstest commented May 17, 2019

I get a System.IO.IOException "Pipe is broken." exception inside PipeServer.cs
LegacyWrapper.Transport.PipeServer::SendCallResponse(CallResult callResult)
{
_fromatter.Serialze(_pipe,callResult);
}

@krisha
Copy link

krisha commented Sep 17, 2020

This happens also in Win 10, but might not be shown to the user except on debugging.

InvokeFunction(data) in ProcessMessages should only be called, when data.Status != KeepAliveStatus.Close (or data.ProcedureName is not null).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants