I'm still debugging while posting :)
So, I said before, that solution compiled with no errors, and that was false. The compilation stopped at the DNN module Store.AddressEdit.ascx.
What I did, is to temporary remove that control from the project and rebuild the solution again.
Now, I don't see anymore DNN related AddressEdit error, but my module errors in the errors list while compiling.
I got 4 errors:
Error 1 Could not load type 'CodexStar.Modules.VideoLinker.ManageAttributes'. C:\Server\TestSite\DotNetNuke\Website\DesktopModules\VideoLinker\ManageAttributes.ascx 1
Error 2 Could not load type 'CodexStar.Modules.VideoLinker.Settings'. C:\Server\TestSite\DotNetNuke\Website\DesktopModules\VideoLinker\Settings.ascx 1
Error 3 Could not load type 'CodexStar.Modules.VideoLinker.EditVideoLinker'. C:\Server\TestSite\DotNetNuke\Website\DesktopModules\VideoLinker\EditVideoLinker.ascx 1
Error 4 Could not load type 'CodexStar.Modules.VideoLinker.ViewVideoLinker'. C:\Server\TestSite\DotNetNuke\Website\DesktopModules\VideoLinker\ViewVideoLinker.ascx 1
Those errors are related to the controls used by my module.
What's strange in here, is that my controls XYZ.ascx are not related to their associated classed(code behind) - XYZ.ascx.cs !
In the solution explorer, I have:
-XYZ.ascx
...XYZ.ascx.cs
XYZ.ascx.designer.cs
The designer is completely appart and not nested inside the control node. What is that?
So the control is searching for it's class (code behind) and cannot find it...
How can it be possible?
Just to remind, I built my module in the newly generated project by DotNetNuke_Community_05.01.01_StarterKit.
After that, I took the XYZ folder and I copied it to the DNN test site, inside the folder Desktop Modules.