Prism - Adding Service References

Is there a recommended way to hook up a prism application to a WCF service? I've tried adding a service reference to my project (it has Prism.UnityExtensions installed via nuget), but whenever I try to update the service references, it throws an error
stating that it didn't update.

On investigating the warnings associated with it, it appears like it's unable to import the wsdl:porttype because it's looking for unity v2.1.505.

As far as I know, there's no official guidance regarding WCF services in
Prism, since Prism is client-side oriented. However, I believe there are examples of how to consume a
WCF service from a Prism application. For example, the following blog post by
Guido Maliandi portrays such scenario:

Thanks Federico. That link looks to be a winner - I'm not trying to use prism on the WCF side (I'll handle that separately), just consume it from a Prism client.

Edit: Scratch that, they aren't really doing anything different per se. I haven't set up settings in the shell app.config yet, but these issues are at design time.

In terms of the error(s), I've install prism.unityextensions via nuget (and let it install prism and unity as necessary), then ran an update-package on the solution to bring everything up to the current version on nuget. When I attempt to perform an "Update
Service Reference" on the reference, I get the below warnings (sorry for the dump):

It seems that your WCF service is asking for Microsoft.Practices.ServiceLocation, which is somehow strange since
ServiceLocation is related to Prism and not
WCF. If your service is referencing ServiceLocation, try removing that reference to see if it solves your problem. If it doesn't, you could also delete the reference to your service from the
Prism side and then reference it again. It is possible that some leftover files from previous builds could be conflicting with newer builds of your service.

If these steps fail to solve your problem, it would be useful if you can provide us with a repro sample of your application or the scenario you are trying to achieve, so that we can analyze it in further detail.

I tested the sample you provided on Visual Studio 2012 and it seems to be working fine. No error or warning messages were shown after opening the sample, and even after a clean build. Therefore, I believe that the root of your problem relies
on your local configuration. I noticed that you seem to be using Visual Studio 2013, which is still in
Preview, so it should be probably related to the errors and warnings you are receiving.