Content tagged as 'Wcf'

Here is a list of all the content that has been tagged as wcf.

Software Engineer Interview Quick Question Set

Redirects to legacy blog post.

Software Engineer Interview Process and Questions

Redirects to legacy blog post.

A short time ago, I was tasked with finding the right software engineer/s for the organisation I was working for. I settled on a process, a set of background questions, a set of practical programming exercises and a set of verbal questions. Later on I cut the set of verbal questions down to a quicker set. In this post, I’ll be going over the process and the full set of verbal questions. In a subsequent post I’ll go over the quicker set.

Sanitising User Input from Browser part 2

Redirects to legacy blog post.

Untrusted data (data entered by a user), should always be treated as though it contains attack code. This data should not be sent anywhere without taking the necessary steps to detect and neutralise the malicious code.

Metadata Exchange options for WCF

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.

Message Inspection in WCF

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.

Duplex communication and callbacks in WCF

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.

Logical vs Physical Addresses in WCF

Redirects to legacy blog post.

In this example, I share a listenUri between two endpoints.

Built-in MSMQ Bindings

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).