AdefWebserver

Read that plus the links they don’t make sense either.  It's not point in telling the reader to delete everything in the files that are created by the dnn module template in VWD 2005 with code.   It’s confusing and doesn’t help.

After gazing at the five different way to achieve the same thing did notice in the cut and paste code the use of the form view but that also lead me down a path to nowhere.

I thought I asked a simple question only to find that there doesn’t seem to be an answer.

How do you trigger the add function event in the controller (I assume it’s in the controller.vb that’s unclear as well) from a button click.  What is the trigger? All I get is confusing mumbo jumbo.

 

doesn’t anyone know the syntax?????  Aslo why would I go to all this trouble to use the DNN functions instead of using straight forward .Net2 functions?  The formview came the closest to being sensible but its not clear how the event is triggered.

can anyone answer the question clearly and concisely

They're trying their best to help you, guy, and everything they have told you is correct. You need to back up a few steps.

1. Can you create a regular, everyday, competely normal UserControl that uses code-behind in a regular, normal, everyday ASP.Net application? If, when you created the control, you selected the appropriate checkbox ("place code is a separate file"), the code-behind is created for you in the same folder as the control's ascx  file.

The App_Code folder generally does not contain code-behind files for controls or pages. It is for components and classes that have no user interface, such as business objects. You're fixated on this folder for some reason. Let it go. Your event handlers belong in your controls' code-behind files and Visual Studio will create them in the same folder as the ascx file. (You can move them, but you need to then edit the path in the Control directive.)

2. Can you drag a button onto the design surface of your newly created UserControl, double-click it in the designer, and see that the code generator created the event handling code in for you in the code-behind file?

3. The only difference between the control you just made and a DNN module is that the DNN module inherits from PortalModuleBase instead of Usercontrol, and otherwise, it is exactly the same process.  You handle events normally and there's nothing special about a module other than the properties and methods provided by the base class.

I'm not sure what you mean by "know the syntax". It's just an event handler for a button, just like normal ASP.Net.

    Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click
    ' Your code here...
    End Sub

You really seem to be making HARD going of a pretty straight forward concept - hmmm -

OK  -  step by step.

Create a folder in \DesktopModules\  called MyModule

Inside there create your module ascx file  TestIt.ascx

<%

@ Control Language="VB" AutoEventWireup="false" CodeFile="TestIt.ascx.vb" Inherits="DesktopModules_WL_System_TestIt" %>
<asp:TextBox ID="TextBox1" runat="server"></asp:TextBox><br />
<asp:Button ID="Button1" runat="server" Text="Button" /><br />
<asp:Label ID="Label1" runat="server"></asp:Label>

Also in the same folder add its code behind module:  TestIt.ascx.vb

Imports

And thats actually all that is needed to get a module working inside DNN

When you hit the BUTTON the sub routine is triggered and the code fires.

NOTE - this is standard ASP.NET code behind syntax - and nothing more - its nothing special.

Westa

DotNetNuke

Partial Class DesktopModules_WL_System_TestIt
   Inherits Entities.Modules.PortalModuleBase

  Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click
     'Your Code Goes here
     Label1.Text = TextBox1.Text & " Clicked"
  End Sub

End Class