Monthly Archives: July 2013

void return methods in WCF (IsOneWay)

Don’t forget, if you’re implementing a fire and forget style method call in WCF, to mark it as one way.

In situations where you do not need or want to return a value from the server or handle exceptions from the client. You must mark the method’s operation contract as IsOneWay=true.

For example (if this is the service contract)

[ServiceContract]
public interface IProjectManager
{
   [OperationContract(IsOneWay=true)]
   void Run();
}

Without the IsOneWay=true the method will get called by the client but will block and may eventually timeout.

Basically with a one way operation the client calls the service and the service may queue the call to be dispatched one at a time. If the number of queued calls exceeds the queue’s capacity the client will block. In the case of a one way call the message is queued but the client unblocked. It is not an async call but may appear that way.

By default IsOneWay is false, hence the need to add the option to the attribute explicitly.

WPF Tips & Tricks

This idea of the tips & tricks is just as a scratch pad for code snippets etc. relating to the subject that don’t warrant a whole post to themselves. Here’s a few WPF tips & tricks.

StringFormat

I seem to always forget this, basically a simple way to apply string formatting to a TextBox (for example) is to use StringFormat

<TextBox Text="{Binding Fahrenheit, StringFormat={}{0:#.##}}" />

The above formats the TextBox string to 2 dp. Fahrenheit in this instance being a float.

Another example with DateTime formatting

<TextBlock Text="{Binding LastUpdateDateTime, StringFormat={}{0:HH:mm:ss dd/MM/yyyy}}" />

Setting the DataContext in XAML

Another one I seem to forget a lot. Admittedly I only tend to use it for simple apps. but still.

<Window.DataContext>
   <Thermometer:ConversionViewModel />
</Window.DataContext>

So we can set the data context on the main window easily enough using this method but there’s also a couple of other ways to create a view model in XAML…

See Settings the DataContext in XAML and the ObjectDataProvider

Order of XAML attributes

A little gotcha to watch out for. Take something like a ComboBox which has the SelectedValue and ItemsSource attributes.

Beware that if SelectedValue appears before ItemsSource you may well find the SelectedValue not set when the binding first takes place. Switch the two around so ItemSource appears first and this should fix the problem.

Detecting whether you’re in design mode

If you need to check whether your control (or general UI) is currently being displayed in design mode, i.e. maybe to not waste time displaying animation or the likes, use

if(!!DesignerProperties.GetIsInDesignMode(this))
{
   // not in design mode
}

Beware d:DesignWidth & d:DesignedHeight as opposed to Height and Width

This is a stupid tip and everyone should know but it’s funny how easy it is to miss this.

I was designing a simple little UI in WPF using both XAML code and the WPF Designer. I made a change to the Width and Height of the control. Unbeknown to me the actual control’s Width and Height were set, not the DesignWidth & DesignHeight. Hence when I placed the control onto another control I couldn’t understand initially why the control was not expanded correctly, when I resized the app.

So beware the WPF designer switching to setting your actual Width and Height as opposed to the d:DesignWidth and d:DesignHeight as it can lead to some head scratching when views are not resizing as expected.

Ix/Interactive Extensions

I’m a bit late to the party with this one – Ix or Interactive Extensions.

Available on NuGet via the Ix-Main package. This will give us the System.Interactive assembly.

Ix are basically a bunch of extension methods for IEnumerable and the
EnumerableEx class. I’m sure many of us have written IEnumerable extensions to supply a ForEach extension method or the likes. Well Ix gives us that and more.

In this post I will not be documenting each overload but will try to give an idea of what the methods might be used for and how to use them. Checking which overload is suitable is down to the reader.

Note: some of the examples may be less than useful, I will attempt to update with better examples as/when I come up with them.

Buffer

Basically takes an IEnumerable and creates an IEnumerable of IList of type T of the given buffer size.

IEnumerable<int> items = new int[] { 3, 5, 6, 2, 76, 45, 32, 1, 6, 3, 89, 100 };
IEnumerable<IList<int>> lists = items.Buffer(3);

The above would result in an IEnumerable with 4 ILists of type T each containing up to 3 items each. An overload of this method exists which allows you to skip a number of elements at the start of each buffer.

Case

Case is a static method on EnumerableEx and allows us to pass in an argument to compare against and an IDictionary of keys – which will be used to match with the argument passed into the Case method and it will return an IEnumerable relating to the values which appear in the dictionary against the given key. So for example

IDictionary<int, IEnumerable<string>> d = new Dictionary<int, IEnumerable<string>>
{
   {5, new[] {"Five"}},
   {4, new[] {"Four"}},
   {1, new[] {"One"}},
   {2, new[] {"Two"}},
   {3, new[] {"Three"}},
};

var matches = EnumerableEx.Case(() => 4, d);

In the above, matches will contain the IEnumerable of the values stored in the dictionary against the key 4, in other words the IEnumerable containing the string “Four”.

An overload of this method allows you to supply an IEnumerable to act as the default values should a match against the selector not be found.

Create

Create is a static method on the EnumerableEx class which allows us to create an IEnumerable from a IEnumerator (or via an overload from an IYielder).

Let’s assume we have a method that returns an IEnumerator of integers, here’s a mock up of such a method

private static IEnumerator<int> Factory()
{
   yield return 1;
   yield return 2;
   yield return 3;
   yield return 4;
}

Now using Ix we can create an IEnumerable of integers using

var items = EnumerableEx.Create(Factory);

Defer

As the name suggests Defer will defer the creation of an enumerable sequence until a call to GetEnumerator, so for example

var items = EnumerableEx.Defer(() => new [] { 3, 5, 6, 2 });

the code above will not call the enumerable factory method (in this case the anonymous method creating an array of integers) until the GetEnumerator is called.

Catch

Creates an IEnumerable sequence based on the source, but if the source has an exception will switch to the second IEnumerable.

A somewhat convoluted sample below

IEnumerable<int> GetNegatives()
{ 
   int[] items = new int[] { -1, -2, 0, -3 };
   for (int i = 0; i < items.Length; i++)
   {
      if (items[i] >= 0)
         throw new Exception();

      yield return items[i];
   }
}

IEnumerable<int> items = new int[] { 3, 5, 6, 2, 76, 45, 32, 1, 6, 3, 89, 100 };
IEnumerable<int> e = GetNegatives().Catch(items);

The above will create an IEnumerable e that contains -1, -2 and then the values from the items IEnumerable.

There are several overloads of the Catch method to check out.

Distinct

Returns an IEnumerable of the distinct values in a sequence

IEnumerable<int> items = new int[] { 3, 5, 6, 2, 76, 45, 32, 1, 6, 3, 89, 100 };
IEnumerable<int> distinct = items.Distinct();

The above will result in a sequence 3, 5, 6, 2, 76, 45, 32, 1, 89, 100 removing the duplicates.

DistinctUntilChanged

Returns consecutive distinct values

IEnumerable<int> items = new int[] { 3, 3, 3, 5, 5, 2, 76, 76, 100 };
IEnumerable<int> distinct = items.DistinctUntilChanged();

The above will return an sequence 3, 5, 2, 76, 100

Do

Several overloads of the Do method exist, we’ll just take a look at the one which takes an Action. Do will simply invoke some action on each item within the IEnumerable, so for example

IEnumerable<int> items = new int[] { 3, 5, 6, 2, 76 };
items.Do(Console.WriteLine);

the above code will simply call WriteLine on each integer within the items IEnumerable. However, this is lazy and hence we actually need to do something with the items returns enumerable.

DoWhile

The DoWhile method iterates over an IEnumerable whilst the supplied function is true, so for example

var items = new int[] { 3, 5, 6, 2 };

int i = 0;
var results = items.DoWhile(() => i++ < 2);
int len = results.Count();

If we run this code the len variable will be 12 as the DoWhile looped through the IEnumerable 3 times and the items array contained four items. So basically if we output to the console each item returned by results will see the array items output three times.

Expand

Expand, basically loops through the supplied IEnumerable (possibly infinitely if you do not use a Take or similar method to stop it). In essence is applies a selector function each time through the enumerable changing the values.

So imagine we have an array of values 1, 2 and 0 and apply Expand to this as follows

var items = new [] { 1, 2, 0 };
var results = items.Expand(i => new[] {i + 1}).Take(9);

what happens here is the output (if we ran results.ForEach(Console.WriteLine)) will output 1, 2, 0 (the values from items then 2, 3, 1 and finally 3, 4, 2. As you see each time we iterate through we add 1 to each element.

Finally

Finally can be used on a sequence so that an action may be invoked upon the termination or disposal, so for example the following will output the sequence to the console then output “Completed”

IEnumerable<int> items = new [] { 3, 5, 6, 2, 76 };

items.Finally(() => Console.WriteLine("Completed")).ForEach(Console.WriteLine);

For

The For method takes a source enumerable and applies a supplied enumerable to it, so a simple example might be

IEnumerable<int> items = new int[] { 3, 5, 6, 2, 76 };
EnumerableEx.For(items, i => new []{i + 1, i + 2});

In this case each item in the items enumerable will have the new []{i + 1, i + 2} applied to it, thus output for this would be

4, 5, 6, 7, 7, 8, 3, 4, 77, 78

the first item 3 in the source enumerable is sent to the For method and we get back a transformed value as two values 3 + 1 and then 3 + 2 and so on.

ForEach

ForEach will invoke an action on each item within an IEnumerable, so a simple example might be to just write a more compact foreach to write output to the console, i.e.

IEnumerable<int> items = new int[] { 3, 5, 6, 2, 76 };
items.ForEach(Console.WriteLine);

Generate

As the name suggests, Generate can be used to generate a sequence in a similar way to a for loop might be used, here’s an example which creates an IEnumerable with the range [10, 20]

EnumerableEx.Generate(10, i => i <= 20, i => i + 1, i => i)

The first argument is the starting value, then we have the condition to stop the generator, next we have the state update function, in this case we’re incrementing the state by 1, finally we have the result function, in this case we’re just using the supplied state value.

Hide

To quote the documentation “Returns Enumerable sequence with the same behavior as the original, but hiding the source identity”.

I’m not wholly sure of the use cases for this, but basically if we have the following

List<int> items = new List<int> { 3, 5, 6, 2, 76 };

if we used items.AsEnumerable() the type returned would still be a List however using

var result = items.Hide();

result will be a funky EnumerableEx type hiding the underlying implementation.

If

The If method is self-explanatory, it allows us to return an IEnumerable if a condition is met or it will return an empty sequence or the overload shown below acts as an if..else returning the alternate sequence

EnumerableEx.If(() => someCondition, new[] { 3, 5, 6, 2, 76 }, new [] {6, 7});

So it’s probably obvious that if the someCondition is true the first array is returned else the second array is returned.

IgnoreElements

A slightly odd one, which probably is more useful when used in combination with other methods. IgnoreElements returns a source sequence without its elements

IEnumerable<int> items = new [] { 3, 5, 6, 2, 76 };
var result = items.IgnoreElements();

result will be an empty sequence.

IsEmpty

As the name suggests, checks if the sequence is empty or not, obviously the following is not empty

IEnumerable<int> items = new [] { 3, 5, 6, 2, 76 };
var result = items.IsEmpty();

whereas the following will be empty

IEnumerable<int> items = new [] { 3, 5, 6, 2, 76 };
var result = items.IgnoreElements().IsEmpty();

Max

Returns the maximum value in the sequence

IEnumerable<int> items = new [] { 3, 5, 6, 2, 76 };
var result = items.Max();

this will result in the result being 76.

MaxBy

In essence MaxBy returns a sequence of values less than the supplied comparer, for example

IEnumerable<int> items = new [] { 3, 50, 6, 2, 76 };
items.MaxBy(i => i < 50).ForEach(Console.WriteLine);

this will create a sequence with values less than 50 and in this case write them to the console, thus outputting the values 3, 6 and 2.

Memoize

Memoize creates a buffer over the source sequence to ensure that if we were to iterate over the items multiple times we would not call the source multiple times. Obviously this would be useful if we’ve got the data from some file system or remote source to stop us retrieving the data multiple times, in use we have

IEnumerable<int> items = new [] { 3, 5, 6, 2, 76 };
var result = items.Memoize();

Min

Returns the minimum value in the sequence

IEnumerable<int> items = new [] { 3, 5, 6, 2, 76 };
var result = items.Max();

this will result in the result being 2.

MinBy

In essence MinBy returns a sequence of values greater than the supplied comparer, for example

IEnumerable<int> items = new [] { 3, 50, 6, 2, 76 };
items.MinBy(i => i < 50).ForEach(Console.WriteLine);

this will create a sequence with values greater or equal to 50 and in this case write them to the console, thus outputting the values 50 and 76.

OnErrorResumeNext

Concatenates the sequence with a second sequence regardless of whether an error occurred, used in situation where you might be getting data from a source that could fail, the example below just shows the syntax really as this wouldn’t need to use OnErrorResumeNext

IEnumerable<int> items = new [] { 3, 50, 6, 2, 76 };
var result = items.OnErrorResumeNext(new[] {9, 10});

result would contain the items sequence followed by the sequence { 9, 10 }.

Publish

To quote the documentation, “creates a buffer with a view over the source sequence, causing each enumerator to obtain access to the remainder of the sequence from the current index in the buffer”.

This allows the sequence to be shared via the buffer, in syntax terms this looks like

IEnumerable<int> items = new [] { 3, 50, 6, 2, 76 };
var buffer = items.Publish();

There is an overloaded method which allows you to supply a selector.

Repeat

Allows us to iterate through a sequence infinitely or with the overload, n times

IEnumerable<int> items = new [] { 3, 5, 6, 2, 76 };

// iterate over three times
items.Repeat(3).ForEach(Console.WriteLine);

// iterate infinitely
items.Repeat().ForEach(Console.WriteLine);

Retry

This method allows us to retry enumerating a sequence whilst an error occurs or via the overload we can specify the maximum number of retries

items.Retry(2);

Return

The Return method returns a single element as a sequence, for example

EnumerableEx.Return(1);

this creates an IEnumerable of integers with the single value 1 in it.

Scan

Scan generates a sequence using an accumulator, so for example

IEnumerable<int> items = new [] { 3, 5, 6, 2, 76 };
items.Scan((i, j) => i + j).ForEach(Console.WriteLine);

will pass 3 (i) and 5 (j) into the accumulator method the result will be 8 this will then be pass into the accumulator as i followed by 6 (j) and so on.

SelectMany

Several overloads exist, the one shown here simply projects each element of the sequence with a given sequence. For example the following simply projects the array { 5, 6 } over the original sequence

IEnumerable<int> items = new [] { 3, 50, 6, 2, 76 };
items.SelectMany(new [] { 5, 6 }).ForEach(Console.WriteLine);

This will output { 5, 6 } the number of times matching the number of elements in the items sequence, i.e. 5 times.

Share

A couple of overloads. This method creates a buffer with a shared view over the sequence so mutiple enumerators can be used to fetch the next element from the sequence, this example is a little convoluted

IEnumerable<int> items = new [] { 20, 10, 60, 30 };
items.Share(x => x.Zip(x, (a, b) => a - b)).ForEach(Console.WriteLine);

The same sequence is used on Zip and passed into Zip hence we’re zipping the sequence with itself, the result selector simply subtracts one value from the other. When output to the console this will write a sequence 10, 30 because the first item (20) has the second item (10) subtracted from it, as then the next item (60) has the final item (30) subtracted.

SkipLast

Allows us to skip/bypass n elements from the end of in the sequence, thus

IEnumerable<int> items = new [] { 3, 5, 6, 2, 76 };
items.SkipLast(2).ForEach(Console.WriteLine);

lists values 3, 5, 6 but not the last 2 items.

StartWith

StartWith starts the sequence with the newly supplied enumerable, for example

IEnumerable<int> items = new [] { 3, 5, 6, 2, 76 };
items.StartWith(new []{9, 10}).ForEach(Console.WriteLine);

will output the sequence 9, 10 then follow with the items sequence.

TakeLast

In essence the opposite of SkipLast, TakeLast results in a sequence on the last n items, such as

IEnumerable<int> items = new [] { 3, 5, 6, 2, 76 };
items.TakeLast(2).ForEach(Console.WriteLine);

which outputs 2 and 76.

Throw

With the Throw method we can create a sequence which throws an exception when we try to enumerate it, for example

EnumerableEx.Throw<int>(new NullReferenceException()).ForEach(Console.WriteLine);

will throw the NullReferenceException when ForEach attempts to enumerate the sequence.

Using

Using creates a sequence which has a resource who’s lifetime is determined by the sequence usage. The idea being the resource is created via the Using method’s first argument then passed to the second argument (in all likelihood to be used in some way) before an IEnumerable is returned. The key thing to note is the resource is not created until we use the returned IEnumerable, for example

IEnumerable<int> items = new [] { 3, 5, 6 };
IEnumerable<int> results = EnumerableEx.Using(() => new SomeDisposable(), resource => items);
results.ForEach(Console.WriteLine);

Assuming SomeDisposable implements IDisposable, when we call GetEnumerator the SomeDisposable is created and passed to the second argument – this rather simplistic example does nothing with the resource but hopefully you get the idea. We then return the IEnumerable and when the GetEnumerator completes the resources Dispose method is called.

While

Loops through the sequence whilst a condition is true, so for example

IEnumerable<int> items = new [] { 3, 5, 6, 2, 76 };

int i = 0;
EnumerableEx.While(() => i++ < 3, items).ForEach(Console.WriteLine);

will output the items sequence three times.

Enumerations in WCF

Like other data types designed to go over the WCF wire (as it were) we need to mark the enum with a DataContractAttribute. Unlike classes, which use the DataMemberAttribute for any published methods we use the EnumMemberAttribute. For example

[DataContract]
public enum Status
{
   [EnumMember]
   None,
   [EnumMember]
   Running,
   [EnumMember]
   Failed,
   [EnumMember]
   Succeeded
}

Don’t forget to add a FlagsAttribute if you are requiring the enum to work as flags otherwise you’ll get an error from WCF when combining your flags, as the value will be unexpected.

Derived and base classes in WCF

This is a short post on something that caught me out, primarily due to the awful client side error message.

The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.

I was implementing a WCF service to allow my client to get historic data from the service. But as the History object might become large I also wanted a HistorySummary object with the bare minimum data. So for example my client UI would list the history summary data and only when the user clicked on the summary would the full data get loaded.

So I implemented my HistorySummary (abridged version below)

[DataContract]
public class HistorySummary
{
   [DataMember]
   public string Name { get; set; }
   // ... other properties
}

From this I derived my History object (also abridged)

[DataContract]
public class History : HistorySummary
{
   [DataMember]
   public string[] Reports { get; set; }
   // ... other properties
}

If you’re experienced in WCF you’ll immediately spot the problem straight away.

I built the server and ran it, no problems. I regenerated the proxies and ran the client and bang ! I get the less than helpful error message shown above.

KnownTypes was the problem. Easy to forget. The base class, HistorySummary should have looked like this

[DataContract]
[KnownType(typeof(History))]
public class HistorySummary
{
   [DataMember]
   public string Name { get; set; }
   // ... other properties
}

The Parallels

The Parallel static class gives us a few nice helper methods to carry out For, ForEach and Invoke methods in a parallel way. In reality we should say a potentially parallel way as there’s no guarantee they will be executed in separate tasks.

Parallel.ForEach

The ForEach method has several overloads, but basically this will loop through an IEnumerable passing each value into an Action. For example

int[] values = new[] { 3, 5, 1, 45, 12, 6, 49 };
Parallel.ForEach(values, Console.WriteLine);

The order in which the Console.WriteLine method is passed values is non-deterministic. In other words there’s no guarantee that 1 will be processed before 45 and so on. A key thing to remember is that all values will be processed before the Parallel.ForEach call returns control to the calling code. In other word a Wait stops the calling code to continue until all items in the enumerable object passed to the ForEach method have been processed.

This means if you run Parallel.ForEach from a UI thread then it will block even though each item placed into the ForEach list is potentially run in parallel. So you need to do something like

Task.Factory.StartNew(() => Parallel.ForEach(values, SomeAction));

Obviously if anything within the action needs to update the UI thread you’ll need to marshal it onto the UI thread.

Parallel.For

Along with the ForEach we also have the For loop. Which allows us to loop from a (inclusive) to b (exclusive) indices calling the supplied Action with the index. For example

int[] values = new[] { 3, 5, 1, 45, 12, 6, 49 };
Parallel.For(0, 2, i => Console.WriteLine(values[i]));

In this instance only “values” 3 and 5 will be passed to the action as we’re starting at (and including) index 0 and stopping before index 2 (as it’s exclusive). The same issues/traits exist for the For loop in that it is blocking etc.

Invoke

Finally we have Invoke which takes an array of Actions and calls them in a potentially parallel manner. Thus if we had several actions that we want to call potentially in parallel we can pass them to the Invoke method to be executed. For example

Parallel.Invoke(() => Console.WriteLine(3), 
                () => Console.WriteLine(4), 
                () => Console.WriteLine(5));

As per For and ForEach this method will potentially execute the actions in parallel but will block the calling thread.

Exceptions

If exceptions occur within the loops or invoke the Parallel library will throw an AggregationException which will contain one or more InnerExceptions.

ParallelLoopState

We can also pass a ParallelLoopState object into either the ForEach or For loops which allows us to Break or Stop a parallel loop as well as allowing us to find out whether a loop has exceptioned or is stopped etc.

ParallelOptions

Each of the For, ForEach and Invoke method have an overload which takes ParallelOptions. This enables us to set the maximum degree of parallelism, the task scheduler and the cancellation token.

The maximum degree of parallelism allows us to limit the possible number of threads uses in a Parallel method.

The cancellation token allows us a way to cancel a parallel task however this is a cooperative operations, in other words the algorithm writer must poll the cancellation token and take the action to cancel the algorithm etc. when the token is set to Cancel. Tasks are not interrupted or stopped in anyway, it’s down to the algorithm to detect and stop.

The task scheduler allows us to assign a custom scheduler to the parallel code.

TypeConverters and XAML

When we’re setting margins, backgrounds etc. in XAML we use string representations which get converted to the actual objects. For example

<Button Margin="0,3,0,3" />

in this example the string 0,3,0,3 is converted into a Margin object by the MarginConverter.

Strings are converted to types using TypeConverters. A simple example of one is listed below

public class AbbreviatedNumberConverter : TypeConverter
{
   public override bool CanConvertFrom(ITypeDescriptorContext context, Type sourceType)
   {
      return sourceType == typeof(string) || base.CanConvertFrom(context, sourceType);
   }

   public override bool CanConvertTo(ITypeDescriptorContext context, Type destinationType)
   {
      return destinationType == typeof(InstanceDescriptor) || 
                 base.CanConvertTo(context, destinationType);
   }

   public override object ConvertFrom(ITypeDescriptorContext context, 
                            CultureInfo culture, object value)
   {
      string text = value as string;
      if (text == null)
      {
         return base.ConvertFrom(context, culture, value);
      }

      if (String.IsNullOrWhiteSpace(text))
      {
         return 0.0;
      }

      if (culture == null)
      {
         culture = CultureInfo.CurrentCulture;
      }

      double number;
      if (AbbreviatedNumeric.ValidateDouble(text, out number, culture))
         return number;

      return 0.0;
   }

   public override object ConvertTo(ITypeDescriptorContext context, 
                     CultureInfo culture, object value, Type destinationType)
   {
      if (destinationType != null && value is Double)
      {
         if (destinationType == typeof(string))
         {
            return value.ToString();
 	 }
      }
      return base.ConvertTo(context, culture, value, destinationType);
   }
}

So the above demonstrated a very simple TypeConverter that converts strings like “134m” into 134000000 or the likes of “10k” to 10000. The actual code for the conversion occurs in the AbbreviatedNumeric.ValidateDouble method which I’ll list at the end of this post but will exclude the tests just to save space. This is not an all encompassing converter, it will only convert k for thousands, m for millions and b for billions and also doesn’t handle multiple languages, but it’s here as an example.

Now let’s assume we’ve created some edit control which has an Amount dependency property which we want to allow the user to enter abbreviated numeric strings into. So the dependency property might look like

public Double Amount
{
   get { return (Double)GetValue(AmountProperty); }
   set { SetValue(AmountProperty, value); }
}

public static readonly DependencyProperty AmountProperty =
                    DependencyProperty.Register("Amount", typeof(Double), 
                    typeof(OnlineStatusControl), new PropertyMetadata(0.0));

To apply our type converter we simple add the TypeConverterAttribute to the Amount property as below

[TypeConverter(typeof(AbbreviatedNumberConverter))]
public Double Amount
{
   get { return (Double)GetValue(AmountProperty); }
   set { SetValue(AmountProperty, value); }
}

and finally when using this new control we can do the following

<Controls:AbbreviatedNumericEditor Amount="123m" />

The type converter is called on this and 123m is converted to 123000000 which is now stored as a Double in the dependency property Amount.

For completeness, here’s the simple AbbreviatedNumeric class

public static class AbbreviatedNumeric
{
   public static bool ValidateDouble(string value, out double? numeric, 
              CultureInfo cultureInfo = null)
   {
      double result;
      if(ValidateDouble(value, out result, cultureInfo))
      {
         numeric = result;
         return true;
      }
      numeric = null;
      return false;
   }

   public static bool ValidateDouble(string value, out double numeric, 
              CultureInfo cultureInfo = null)
   {	
      if (String.IsNullOrEmpty(value))
      {
         numeric = 0;
         return false;
      }

      if (Double.TryParse(value, out numeric))
      {
         return true;
      }
      if (value.Length > 0)
      {
         if (cultureInfo == null)
         {
	    cultureInfo = CultureInfo.CurrentCulture;
	 }

	 NumberFormatInfo numberFormat = cultureInfo.NumberFormat;
 	 if (value.Substring(0, 1) == numberFormat.NumberDecimalSeparator)
	 {
	    value = "0" + value;
	 }
	 if (Double.TryParse(value.Substring(0, value.Length - 1), 
                     NumberStyles.AllowLeadingWhite | 
                     NumberStyles.AllowTrailingWhite |                      
                     NumberStyles.AllowLeadingSign |
 		     NumberStyles.AllowDecimalPoint | 
                     NumberStyles.AllowThousands | 
		     NumberStyles.AllowExponent, cultureInfo, out numeric))
	 {
	    switch (Char.ToUpper(value[value.Length - 1]))
	    {
	        case 'B':
		   numeric = numeric * 1000000000;
		   break;
		case 'M':
		   numeric = numeric * 1000000;
		   break;
		case 'K':
		   numeric = numeric * 1000;
		   break;
		default:
		   return false;
	    }
            return true;
	 }
      }
      return false;
   }
}

How to exclude code from code coverage

In Visual Studio 2012 we can run code coverage analysis across our code (for example across our unit test suite). But we might not want to have all code analysed. For example I don’t really want to see the test classes as part of the analysis but do want to see the code under test.

So we can exclude code from the code coverage analysis using the ExcludeFromCodeCoverageAttribute. This can be applied to methods, properties, classes, structs etc.

An attempt was made to access a socket in a way forbidden by its access permissions

Was implementing a WCF service and found that I was getting the following error

A TCP error (10013: An attempt was made to access a socket in a way forbidden by its access permissions) occurred while listening on IP Endpoint=0.0.0.0:8733

In this case the problem was down to an existing service running on the port, use

netstat -a

to see if the port has already been taken

Mixed mode assemblies exception

Occasionally I get caught out by an assembly in .NET having been compiled in, say, .NET 2.0 and now wanting to use it in a newer version of .NET, for example .NET 4.0.

You’ll probably see an error like the following

System.IO.FileLoadException: Mixed mode assembly is built against version ‘v2.0.50727’ of the runtime and cannot be loaded in the 4.0

Obviously if I could recompile the offending 2.0 assembly I would, but this occasionally happens with libraries such as those imported into an application via NuGet and I really don’t need the headache of finding the original source and rebuilding.

So to fix this simple add the following to the App.Config in the configurations section

<startup useLegacyV2RuntimeActivationPolicy="true">
   <supportedRuntime version="v4.0"/>
</startup>