private void StartService()
{
Logger.Log("Starting in session server for session " + _sessionId);
_process = ProcessHelper.Start(_sessionId, Assembly.GetEntryAssembly().Location, Program.InSessionSwitch);
// TODO: now that we are running as an administrator, we could probably use the named pipes binding.
// Using the named pipes binding here is problematic when running as a limited user, as described here:
// http://weblogs.thinktecture.com/cweyer/2007/12/dealing-with-os-privilege-issues-in-wcf-named-pipes-scenarios.html
_testService = ChannelFactory<IInSessionTestService>.CreateChannel(new NetTcpBinding(),
new EndpointAddress(
InSessionServer.EndpointUri));
}
private void StartService()
{
Logger.Log("Starting in session server for session " + _sessionId);
_process = ProcessHelper.Start(_sessionId, Assembly.GetEntryAssembly().Location, Program.InSessionSwitch);
// TODO: now that we are running as an administrator, we could probably use the named pipes binding.
// Using the named pipes binding here is problematic when running as a limited user, as described here:
// http://weblogs.thinktecture.com/cweyer/2007/12/dealing-with-os-privilege-issues-in-wcf-named-pipes-scenarios.html
_testService = ChannelFactory <IInSessionTestService> .CreateChannel(new NetTcpBinding(),
new EndpointAddress(
InSessionServer.EndpointUri));
}
