If this were strictly a c# module, you would need to add a key to the codeSubDirectories section of the web.config file. For a module named TestModule you would add:

[add directoryName="TestModule" /]

(Replace the square brackets by the angle brackets in web.config)

So ... I'd try that.

IF that doesn't work, it's likely because the mixed language part. In that case you might want to compile the c# class into a dll. Or, you might want to translate and make the module single-language. On occasion, I've used some translator web sites to translate with success.

Hey Joe,

Thanks for the reply.

I just realized that your forums remove angle brackets, the origal post should have read (where [ ] = angle brackets AND [[  ]] = one square bracket) as in the .dnn manifest file.


[file]
    [path]      [[app_code]] \ cs    [/path]
    [name]   myClass.cs    [/name]
[/file]

etc.....

I also understand about the required "codeSubDirectories" entry in web.config.  My question is really:

How do I describe a source file in the .dnn (manifest file) so that the file is installed correctly in "/App_Code/cs" AND is there a way during the moduel install process where I can programmatically add the codeSubDirectories stanza to the web.config.  Surely there must be a way. 

The module in question is done for hire.  It must be packaged with source code and will be installed on more than one site/machine.  The cusotmer does not want the admins to have to edit the web.config file just to install a module.

Translating the C# to vb is not an option.  I may be resigned to translating the wrapper to C#, but then I think I have the same problem, as the rest of the target sites are all vb all the time.

Regards,
    rock

Do I understand that you have the module working, and that it's just a matter of getting the install package set up correctly?

If you need to stick a file in the app_code section, use something like (use angle brackets!):

[file>\]
[path][app_code][/path]
[name]WarningInterval.cs<[/name]
[/file]

I found a "DNN Project Packager" at http://www.codeproject.com/useritem...kager.asp.

I'm not aware of how you include the web.config changes in the dnn file, but I'm sure that it exists. I'll look around.

Hey Joe,

Eh, we're almost on the same page....  I think we drifted because of the missing angle brackets on the original post?  Oh well, not to worry.

You are correct in that the module is working just fine, it's the install procedure that's giving us a hard time.  If you look back at the first post, the code (in blue) are the different ways I tried to describe the files in the .dnn file ( [file][/file] & [name][/name] are of course missing in the post).  None of them put the .cs files in the correct place.  Somehow, via the manifest file (or if there is a way to attach a script), I need the .cs files to end up under:

"/App_Code/cs"

so that they will compile. 

You can see from the original post that I tried:

[app_code]
[app_code]\cs
App_Code\cs
"\App_code\cs"

without success (refer to original post for outcome of each).

I am going to download the "Packager" you found and see if it does it correctly, if so I will post the procedure here.

Thanks again!
- rock

did you use the "path" tags?

Hey Joe,

yep, used the path tags.  I pasted the .dnn below but I have replaced the angle brackets with braces {}.

As you can see in the version below I was last trying "{path}[app_code]\cs{/path}" but this placed the .cs files in:
" \App_code\ModuleName\cs" and the complier won't find them.

BTW: I downloaded the "Packager" and it does not handle this situation.

Regards,
- rock

-------------------------------------------------------------------------------------------------------------------
{dotnetnuke version="3.0" type="Module"}
    {folders}
        {folder}
            {name}BluesmanMedia.Sim{/name}
            {friendlyname}Sim{/friendlyname}
            {foldername}Sim{/foldername}
            {modulename}BluesmanMedia.Sim{/modulename}
            {description}A Sim module{/description}
            {version}01.00.00{/version}
            {businesscontrollerclass}BluesmanMedia.Modules.Sim.SimController{/businesscontrollerclass}
            {modules}
                {module}
                    {friendlyname}Sim{/friendlyname}
                    {cachetime}0{/cachetime}
                    {controls}
                        {control}
                            {src}DesktopModules/Sim/ViewSim.ascx{/src}
                            {type}View{/type}
                            {helpurl}{/helpurl}
                        {/control}
                        {control}
                            {key}Edit{/key}
                            {title}Edit Content{/title}
                            {src}DesktopModules/Sim/EditSim.ascx{/src}
                            {type}Edit{/type}
                            {helpurl}{/helpurl}
                        {/control}
                        {control}
                            {key}Settings{/key}
                            {title}Sim Settings{/title}
                            {src}DesktopModules/Sim/Settings.ascx{/src}
                            {type}Edit{/type}
                            {helpurl}{/helpurl}
                        {/control}
                    {/controls}
                {/module}
            {/modules}
            {files}
                {file}
                    {name}ViewSim.ascx{/name}
                {/file}
                {file}
                    {name}ViewSim.ascx.vb{/name}
                {/file}
                {file}
                    {name}EditSim.ascx{/name}
                {/file}
                {file}
                    {name}EditSim.ascx.vb{/name}
                {/file}
                {file}
                    {name}Settings.ascx{/name}
                {/file}
                {file}
                    {name}Settings.ascx.vb{/name}
                {/file}
                {file}
                    {path}App_LocalResources{/path}
                    {name}ViewSim.ascx.resx{/name}
                {/file}
                {file}
                    {path}App_LocalResources{/path}
                    {name}EditSim.ascx.resx{/name}
                {/file}
                {file}
                    {path}App_LocalResources{/path}
                    {name}Settings.ascx.resx{/name}
                {/file}
                {file}
                    {path}[app_code]{/path}
                    {name}DataProvider.vb{/name}
                {/file}
                {file}
                    {path}[app_code]{/path}
                    {name}SimController.vb{/name}
                {/file}
                {file}
                    {path}[app_code]{/path}
                    {name}SimInfo.vb{/name}
                {/file}
                {file}
                    {path}[app_code]{/path}
                    {name}SqlDataProvider.vb{/name}
                {/file}

                {file}
                    {path}[app_code]\cs{/path}
                    {name}Analysis.cs{/name}
                {/file}
                {file}
                    {path}[app_code]\cs{/path}
                    {name}Evaluator.cs{/name}
                {/file}
                {file}
                    {path}[app_code]\cs{/path}
                    {name}Iterator.cs{/name}
                {/file}
                {file}
                    {path}[app_code]\cs{/path}
                    {name}Pockets.cs{/name}
                {/file}
                {file}
                    {name}01.00.00.SqlDataProvider{/name}
                {/file}
                {file}
                    {name}Uninstall.SqlDataProvider{/name}
                {/file}
            {/files}
        {/folder}
    {/folders}
{/dotnetnuke}
------------------------------------------------------------------------------------------------

You should probably take at look at the DotNetNuke Module Developers guide and other resources available here.  I've only built simple .dnn files by hand.

That guide takes you through the process of creating a module in a DotNetNuke development environment.  When you have the module finished, there is a "Create Module Package" link at the bottom of the module definitions page that should create the package for you.  There is also a description of how to create compiled versions of your module so that you don't have to distribute source code.  Doing that, you don't have the compilation issue in web.config either.

Thanks Joe,

Unfortunalty the client wants the source included in the package and the .dnn file I have was created by the "Create Module Package" link.

I'll keep poking around, there's bound to be a solution somewhere....  i have a few more things I can try... I think....

Thanks again!

- rock