While I am not specifically aware of a public DotNetNuke-specific example that consumes a WCF service (although examples likely exist), there will be very little difference in consuming such a service via DotNetNuke than in a regular ASP.NET application.  The only real difference that comes to mind is the fact that, in your installation manifest, you will need to ensure that your service metadata gets merged into the installation web.config.

So, just as in a "regular" ASP.NET application, add your service reference, ensure your service metadata is correct in your web.config, and then just consume the service.  WCF tends to be pretty unforgiving, so if you encounter further errors they are unlikely to be related to the fact that you're inside a DotNetNuke module.

Hope this helps!

Brandon

---

Brandon Haynes
BrandonHaynes.org