In the Visual Studio project for The Monack Framework packages are load dynamically. With this architecture there are no references from the main project to the package project which causes the package project not to built when the main project is built. In this post I will explain how to make sure all projects are built, even if there is no reference to that project.
In this final post of my series about WCF I will show you how to make a WCF service available by hosting it in executable code. In the example I use a console application. In a real world situation this should be a windows service but for debugging purposes and since this is only a proof of concept I use a console app.
The nice thing of WCF is that you can easily switch connection methods. the only thing you need to change is some configuration and the type of the connection classes you’re using. All other code remains the same.
In this fourth post of my series about creating and using a WCF service, I'll show you how to create a WCF service that accepts TCP connections. TCP should be faster than using the service over HTTP since there is less overhead, but a complete performance analysis is beyond the scope of this article.
In previous posts I described how to create a basic web service and connect to it without using a proxy generated by Visual Studio. The next step is to describe how to setup IIS to use WCF through Http and connect to it with a client.