I am developing a number of modules for a client that will share some user interface functionality using a common Web User Control to provide the UI. When I wrote the first module and added in the .ascx file, all was fine. When I add the same control to the second module, I get the following error:

DotNetNuke.Services.Exceptions.ModuleLoadException: The type 'XXX.ParametersControl.ParameterTabControl' is ambiguous: it could come from assembly 'C:\Clients\XXX\Code\Reporting\DotNetNuke_BaseInstall\bin\XXX.KPI_Configurable_Chart.DLL' or from assembly 'C:\Clients\XXX\Code\Reporting\DotNetNuke_BaseInstall\bin\XXX.Survey_Grid.DLL'. Please specify the assembly explicitly in the type name.

Both modules install and run just fine without this additional UI control.

I developed the UI control as a separate project that compiles it's own DLL for the included back end functionality, then deploy the application with just the compiled DLL and the control ASCX file in the module install files. 

The include into the main module ASCX is done this way:

 

<%@ Register src="ParameterControl/ParameterTabControl.ascx" tagname="ParameterTabControl" tagprefix="uc1" %>
<uc1:ParameterTabControl ID="ParameterTabControl1" runat="server" />

 

As you can see, I include the interface control by getting it from a subdirectory, which I implement as a Subversion external.

I reference the control's objects and properties in the main module's .vb codebehind like this:

                ParameterTabControl1.DateRangeTabVisible = True
                If (ParameterTabControl1.StartDate Is Nothing) Then
                    ParameterTabControl1.StartDate = DateAdd(DateInterval.Day, -90, Now)
                End If

Any tips on how to engineer this so it doesn't happen? Some way to get the sub-control ASCX to connect only to it's own DLL and not be bound to the main module control while still allowing me to query properties and objects on the control to set and get it's properties?