I have some .net end code that I need to get locally from my application to connect to a Win8 network.
It would be better to expose the end-of-code code through WCF services. I assume the .nettcp binding will work? or it would be better to create a broker window runtime component as described here: https://code.msdn.microsoft.com/windowsapps/Brokered-Windows-Runtime-9d64cada
After examining this question, I found that you can call WCF services using NetTcpBinding, but not NetNamedPipeBinding. A list of supported bindings can be found here: http://blogs.msdn.com/b/piyushjo/archive/2011/10/19/wcf-for-metro-apps-supported-functionality.aspx
I decided to follow the Brokered WinRT component path for performance reasons. This is a very good article to help you get started: http://devhawk.net/2014/04/25/brokered-winrt-components-step-one