About a week ago I began trying to connect to an internal WCF web service. I received the error
Custom tool error: Failed to generate code for the service reference 'DynamicsCom'. Please check other error and warning messages for details.
Unforunately the only other errors pointed towards the same basic problem: my solution was unable to bring down the namespace used by the WCF web service. In fact, the Reference.cs
class is completely blank save for the auto-generated comment.
Reference.cs
//------------------------------------------------------------------------------
// <auto-generated>
// This code was generated by a tool.
// Runtime Version:4.0.30319.18063
//
// Changes to this file may cause incorrect behavior and will be lost if
// the code is regenerated.
// </auto-generated>
//------------------------------------------------------------------------------
Everything I've read on the internet suggests I got to Configure Service Reference
and uncheck Resuse types in referenced assemblies
. And while this does work, in bringing down the namespace used in the WCF web service, it unfortunatley creates a number of other conflicts.
Both my project and the web service namespace use the Mircosoft CRM SDK, and when I uncheck the Reuse types in referenced assemblies
checkbox a number of namespace "ambiguities" occur (between the SDK dll referenced in the solution and the web service namespace).
My question is: is there a way to specifically debug the causes behind the namespace not being brought down from the web service? The common solution just seems like a blanket approach that doesn't always diagnose the real problem.