When I first add a new .ascx user control in VS2005 to my DNN module's folder, I find that the second form of the @Control directive is set up by default and in the codefile the class receives a corresponding name - in your case "DesktopModules_XContactus_XContactus.  Because I prefer to use consistent Namespace like WESNet.DNN.Modules.ModuleName.ClassName I have to manually add a Namespace statement to the Codefile, and change the class name. Corresponding changes must be made in the @Control Inherits attribute in the .ascx file.  So, I end up with:

<% @Control . . . Inherits="WESNet.DNN.Modules.EPrayer.PostPrayer" . . %>

and

Namespace WESNet.DNN.Modules.EPrayer
     Public Class PostPrayer
          Inherits PortalModuleBase

     End Class
End Namespace

In a VS2003 module project, I was able to set my root namespace and have it used automatically each time a new user control or class was added.  This seems to be missing in VS2005 unless I'm using a Web Application Project.  What am I missing?

So, it appears that either method is correct - as long as the Inherits attribute in the control matches the combination of explicit namespace and class name in the Codefile.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

Did you mean "Partial Class PostPrayer" ? Without the "Partial" that changes things a bit.

---

Michael Washington
http://ADefWebserver.com

A Free Open Source DotNetNuke Help Desk Module