Developer forum

Hi Regin

You can have your code in another assembly than CustomModules.dll - when the solution is open, you can right click the solution in VS 2005s solution explorer, choose properties and change the assembly name and rootnamespace (both should be changed to the same).

The only thing the other solution partner needs to do is add a call to the module in the CustomModuleHandler of Default.aspx.vb/cs:

Public Class CustomModuleHandler

Public Sub GetCustomModule(ByVal sender As Object, ByVal e As Dynamicweb.Frontend.CustomModuleEventArgs)

Dim strModuleName As String = e.Name

Select Case strModuleName

Case "CustomHello".ToLower

Dim myCustomHello As New CustomHello

e.Output = myCustomHello.Hello(e.ParagraphRow, e.Pageview)

End Select

End Sub

End Class

After doing this you are able to upload your assembly and aspx files with changes without changing the original custommodule.dll.

If needed you will also be able to "take over" the Default.aspx file and the code of Default.aspx.vb/cs - just upload your version of the Default.aspx where the @page directive:

In stead of this

<%@ Page AutoEventWireup="false" Codebehind="Default.aspx.vb" CodePage="65001" Inherits="CustomModules._Default" Language="vb" ValidateRequest="false" %>

Should be something like this:

<%@ Page AutoEventWireup="false" Codebehind="Default.aspx.vb" CodePage="65001" Inherits="YourNewAssemblyName._Default" Language="vb" ValidateRequest="false" %>

Just remember to make references to the modules provided by the first solutionpartner in the CustomModulesHandler