What you are saying makes sense, but I'm a nubie. I can edit the ascx file, but thats where it all ends. No idea how to pack it and upload it..I took a quick glance at the module dev's tutorial, but it's all Visual Studio stuff, which is out of my ballpark for now..

Anyway, I edited the manageusers to hide the delete and roles buttons, like this (simply commented them out);

<p>
 <asp:linkbutton class="CommandButton" id="cmdUpdate" resourcekey="cmdUpdate" runat="server" text="Update"></asp:linkbutton>&nbsp;
 <asp:linkbutton class="CommandButton" id="cmdUnlock" resourcekey="cmdUnlock" runat="server" text="Unlock Account"
  CausesValidation="False" Visible="False"></asp:linkbutton>&nbsp;
 <asp:linkbutton class="CommandButton" id="cmdCancel" resourcekey="cmdCancel" runat="server" text="Cancel"
  causesvalidation="False" borderstyle="none"></asp:linkbutton>&nbsp;
<%-- <asp:linkbutton class="CommandButton" id="cmdDelete" resourcekey="cmdDelete" runat="server" text="Delete"
  causesvalidation="False"></asp:linkbutton>&nbsp; --%>
<%-- <asp:linkbutton class="CommandButton" id="cmdManage" resourcekey="cmdManage" runat="server" text="Manage Security Roles"
  causesvalidation="False"></asp:linkbutton> --%>
</p>

Is that the right track? And can you give me pointers on how to install this "module" now?

Thanks again!

If you're not that familiar with VS/.NET, then you might want to get another module for now. If you are interested in trying it all out, however, I really suggest you read thru the module developers guide (in the DNN documentation release). Basically, you'll need to create a new module directory in the DesktopModules directory, copy (and modify) the Users.ascx and ManageUsers.ascx controls (you probably won't have to change the Users.ascx control), and register it on the Host > Module Definitions page. To package it up, all you need is to zip up your .ascx files and create a .dnn metadata descriptor. You should copy one of the core module's .dnn file for a starting point - I suggest a simple module, like the Image module, for instance.

When you register the module definition and controls, the Users.ascx control should have a null key and a type of View. The ManageUsers.ascx control should have both a key and type of Edit.

The docs should tell you everything you need to know about registering module definitions and creating the .dnn file.

---

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com

Michael,

I realize this tread is old but I am currently attempting exactly what you describe here. I wonder if you could clarify...

When you say 'Basically, you'll need to create a new module directory in the DesktopModules directory, copy (and modify) the Users.ascx and ManageUsers.ascx controls' should I create folders 'DesktopModules/Users/users.ascx and DesktopModules/ManageUsers/manageusers.ascx' or just one folder ''DesktopModules/Users' and put both controls in it?

I tried it the last way and I can add the users module no problem but the manage users module appears in the module drop down list but when I add it to the page it does not show up.

Further, once the module definitions are added, would I then add both modules to a single page? I guess so, right?

Frank