WCF offers very flexible approach of Input and Data Validation based on XML Schemas. The approach is flexible since the validation rules are expressed in form of XML schema and can be changed at any time without recompiling the solution.

I followed the steps detailed in How To: Perform Message Validation with Schema Validation in WCF and ended up with another working sample (imagine that!).

It took me a bit to struggle with the schema thing and then enabling debugging info on the service side (remember, WCF is secure by default) to understand what's going on and why it fails time after time.

In the end me and WCF made friends and I'd thought it'd be good to share with you the Visual Studio project. Download it here from my SkyDrive and save yourself some time.

My related posts

• WCF Security - Input/Data Validation Sample Visual Studio Project

Enjoy.

Input and Data Validation is one of the core security principles. WCF is no exception. To get most out of WCF in secure way one must implement proper Input and Data Validation.

I was following instructions on How To – Perform Input Validation in WCF compiled by patterns&practice team lead by JD Meier.

In a nutshell the process consists of creating 3 classes and tweaking a config file a "bit".

From the guide:

• Step 4 – Create a Class That Implements the Validation Logic
• Step 5 – Create a Class That Implements a Custom Endpoint Behavior
• Step 6 – Create a Class That Implements a Custom Configuration Element
• Step 7 – Add the Custom Behavior to the Configuration File
• Step 8 – Create an Endpoint Behavior and Map It to Use the Custom Behavior
• Step 9 – Configure the Service Endpoint to Use the Endpoint Behavior

I ended up with working sample built with Visual Studio 2008. I though it'd be good idea to share it to help you boost your productivity.

Grab the Visual Studio project on my SkyDrive here.

Enjoy

Field experience proves - the earlier performance is tackled in development lifecycle the better results achieved. Below are most frequent practices that were most helpful in my engagement with the customers.

Architecture/Design phase

• Set performance scope using Performance Frame
• Set performance objectives - Performance Testing Objectives Document Template
• Generate and distribute performance engineering principles document to the dev team (this sample was generated using Guidance Explorer)
• Conduct performance design inspection (this sample document was generated using Guidance Explorer)

Coding phase

• Conduct static code analysis for performance issues - Performance Code Review Tool – Practices Checker
• Conduct manual performance code inspection using checklist document (this sample was generated using Guidance Explorer)
• Analyze program's flow early in development - Use Sysinternals DebugView To Diagnose The Application

Unit testing phase

• Conduct performance smoke test for your application - Stress Test ASP.NET Web Application With Free WCAT Tool
• Analyze IIS behavior - Identify ASP.NET, Web Services, And WCF Performance Issues By Examining IIS Logs
• Analyze Database behavior using SQL Server profiler - How To: Use SQL Profiler and Using SQL Server Profiler
• Analyze Client Side JavaScript behavior -  Profiling JavaScript With Ajax View Tool: Spot Poor Performance Client Script In No Time
• Analyze ASP.NET behavior - Use Performance Counters Templates To Streamline Performance Analysis
• Analyze HTTP traffic from end user's angle - Improve Web Application Performance By Reducing Number Of Http Requests - Fiddler To The Rescue

Performance Sins (performance anti-patterns)

• Performance Sin - Chatty Database Access And Loops (Plus Another Free Performance Tool)
• Performance Sin - Using Exceptions To Control Flow 
• ASP.NET Performance Sin - Serving Images Dynamically (Or Another Reason To Love Fiddler)

My related posts

• Do You Really Need A Distributed Architecture?
• Improve .Net Applications Performance Effectively And Efficiently
• Generate Your Own Security Code Review Checklist Document Using Outlook 2007
• Consume patterns&practices Guidance Explorer online store via RSS
• How To Keep ASP.NET ViewState On The Server – Revised