kickinhard wrote
I finally got it to work (sp1 update) but yet again I come across some problems:
-
Currently we use the duallistcontrol from dnn in our project. (Which of course cannot be found? Trying to make a compiled module)
-
We use allot of teleric components so in the code we have things like this “RadControlsDir="~/controls/RadControls/" (which of course also cannot be found)
-
We also cannot clear Default Namespace from within the properties.
-
Why must the Default namespace be null? (Because in every class we have at the moment we use a Default Namespace).
What kind of approach could we use to fix all of this?
Thanks in advance
Hi
Ok, in design view when looking at your module you won't be able to see the control since the path will be something like ~control/dnnlabel.ascx.
This folder doesn't exist in the project at this module level. However you will be able to compile and run without issue. This is more todo with how VS design mode works.
More importantly you will be able to call methods/properties on the controls in your code since you have a reference to the DotNetNuke.dll assembly which contains the code behind class for the controls.
If you are using other components you'll have to make sure their assembies are added as references in your module. I.e the teleric controls.
The default namespace thing doesn't matter too much, you could just leave as is. Here is the snippet from MSDN which explains this setting.
Specifies the base namespace for all files in the project. For example, if you set the root namespace to
Project1 and you have a
Class1 outside of any namespace in your code, its namespace would be
Project1.Class1. If you have a
Class2 within a namespace
Order in code, its namespace would be
Project1.Order.Class2.
It is also possible to clear the root namespace property, which allows you to manually specify the namespace structure of your project.
Regards
Mark