Hi !
Know that I managed to create a module for DNN4, I tested the deployment as well and ran into a problem. I don't want to give away the source so I followed Shaun Walker's directions #2 (http://forums.asp.net/1114393/ShowPost.aspx). I made up a manifest file, zipped everything and installed it to a second DNN installation (on the same machine). The upload and installation as such were no problem.
The problem is, that the ascx does not find the (compiled) class from the codefile. The errormessage is "Could not load type namespace.classname". All necessary code is of course compiled and copied to the bin folder.


As soon as I copy the ascx.vb files also anything works fine...

Any hints / ideas?

Cheers, carsten

I already got VS 2005 pro and I even precompiled my developement environment including my own module.
Now I have one .dll based on the the code in the App_Code Folder of DNN4 and one App_Web_*.ascx.dll for each codebehind file.
I packaged everything in a zip file and uploaded the module in an other testing env. Uploading worked perfectly.
The problem is, that the ascx files of the module (like settings.ascx) do not find the (compiled) class from the code behind file. The errormessage is "Could not load type myCompany.Module.View.CodeBehindClass". All necessary code is of course compiled and copied to the bin folder.

It's really strange cause every other namespace like "myCompany.Module.Data" can be used / accessed.
Only the ones defined in the codebehinds cannot be used in the *.ascx files.

You guys ever figure this out?

In the vb:
Namespace PortVista.Modules.MyModule
    Partial Public Class View
        Inherits DotNetNuke.Entities.Modules.PortalModuleBase

...

In the ascx:
<%@ Control Language="vb" AutoEventWireup="false" CodeBehind="View.ascx.vb" Inherits="PortVista.Modules.MyModule.View" %>
...


Am I missing something?

---

Jason Honingford - Web & Software Developer
www.PortVista.com