Browse by Tags
All Tags »
.win.fx (
RSS)
WCF's configuration is somewhat complex and the first time you start using it can been daunting. Below is an image of the schema published by Microsoft. You can print this out on a A3 or something and use it has a handy reference.
The WPF wiki on Channel 9 has a WPF Application Portfolio - some are cool and some are surprisingly useful. Many of these can be deployed with ClickOnce making it convenient. If you are not on Vista you will need the .NET 3.0 bits.
This is quite cool; I got this via one of the Avanade communities. The .NET CF team is working to port WCF to the compact framework and as you can see below it will support a subset of the WCF. You can get more details on this post by Roman, though there are more WCF details on that and not as much as the WCF "Compact Edition", it is still quite exciting...
Nope it is not 1 minute or even 60 seconds rather is 59.9990235 seconds
I found this very irritating behavior with WCF (at least with the Vista RC2 runtime of WinFX, I have not tried it with the other builds yet). When I am on an active VPN connection (in this case, connected to the Avanade corporate network) and I try and start a new WCF Service it fails spectacularly with a NetworkUnreachable exception. When I disconnect from...
I don't know if I am doing something wrong, or if this is a bug (it has been a long day for me and I am at wit's end so I cannot be certain one way or the other). If you have a WCF class (for example as shown in the code snipped below), where I have a Windows Form that happens to implement both the Service and Client side of a WCF application. 1 [ServiceBehavior...
You probably know that I am co-authoring a book along with a few other fellow Avanader’s and ex-Avanader’s who I call the Indigo Amigos. Who are these crazy people you ask? Brave enough to hang out with me. In addition to reading their names on APress or Amazon , but here are the links to their blogs/sites in ascending order: Aftab Chopra Chris...
Well I suppose I can talk a little about it now - after all it seems like happening. For the last few months I and a few other colleagues of mine are writing a book on Indigo, now called WCF (Windows Communication Framework). I personally am quite fascinated by communication and all the challenges that brings to the table. The book is titled "Pro WCF: Practical...
If anyone knows I would love to know what the reasoning was behind calling the Indigo (now WCF) namespace as System.ServiceModel ? Why Model, why not just Service (though it might get confusing with the Windows Services), or something else? To me its not very intuitive, I am use to it now, so its almost like second nature, but would still be good to know...