Redirects to legacy blog post.
I’ve been working on a small project that shuts down machines attached by network and of course power feed to an APC Smart-UPS. The code that was shutting down the guests required authentication to be passed to the receiving services.
Redirects to legacy blog post.
There are two options for publishing metadata from a WCF service. By default, the services metadata is not published. In order to make the services information about itself public, you must do either of the following.
Redirects to legacy blog post.
Message Inspectors can be a very usefull tool in diagnosing problems between WCF services and clients. The messages that are transferred between clients/services can be intercepted and operations performed on them. We’ve used this at work in conjunction with a tool called SaopUI to capture the SOAP messages and fire them at our service. This can be usefull for load testing, concurrency testing scenarios amongst others.
Redirects to legacy blog post.
I was reading in the book Enterprise Integration Patterns that my dev manager bought for the team, on the Message Endpoint pattern on the way home from work a few days ago.
“A Message Endpoint can be used to send messages or receive them, but one instance does not do both” From my experience, this wasn’t necessarily true. So I decided to confirm my suspicion.
The following is a mix of what I read and tested out.
Redirects to legacy blog post.
`NetMsmqBinding` only works if you have WCF on both sides of the Queue-to-Queue transfer. `MsmqIntegrationBinding` is targeted toward existing MSMQ applications that use COM, native C++ APIs or the types defined in the `System.Messaging` namespace (as stated by MSDN).