It is usually one of three things, by the look of it. Check them in this order:

1. Namespace issue, in that the markup file claims to inherits from a partial code-behind class of a different namespace. Usually happens in all environments, not just development or live.
2. It is caused by a reference from the module's project file (WAP project development) to an assembly which is of a version that is different in the working environment to that in the non-working environment. This is mostly an issue for strongly-named assemblies (DotNetNuke.dll is not strongly named, so it's not likely to be that one). Check the versions shown in the references page of the project against the actual file versions in the Bin folder.
3. You sometimes need to add a compile-time reference to an assembly that is consumed by the project. This is particularly true for assemblies in the GAC, where you need to add an <%@ Register Assembly="Blah, Version=x.x.x.x, Culture=neutral, PublicKeyToken=lotsofnumbers" namespace="SomeNamespace" tagprefix="something" %> in the markup of the control, or add an <assembly> reference in web.config.

Hope this helps. This last one threw me for one of mine; I don't understand exactly why the particular control that caught me out needed this, as it did not appear to be directly referencing the file; however I was loading the control dynamically and its code-behind referred to an assembly that referred to the one I needed to add. It does not appear to be required in all circumstances, only in some specific circumstance that I have failed to grasp!