|
|
I'm curious how others are dealing with the issue of asp.net controls wanting to see a web.config file within the module project. Currently I am renaming the web.config file when I want to test the module within my dnndev site. I then rename
the web.config file back to it's correct name when switching back to development mode. This works, but is very cumbersome.
|
|
Coordinator
Jun 1, 2012 at 9:39 PM
|
I remove the web.config from the folder whenever it gets added. Which controls are you having troubles with?
|
|
|
|
Chris, thanks for the prompt reply. The problem I'm having seems to be with the ajax updatepanel. I don't know if the controls inside the panel will render, since I can't see them. Is there an alternative to the MS ajax updatepanel from
telerik?
|
|
Coordinator
Jun 1, 2012 at 9:49 PM
|
I haven't used an update panel in quite a while, though you can have DNN wrap your module in an update panel using the "supports partial rendering" options in the module definition, that would remove the requirement for putting the panel in your own controls?
|
|
|
|
I'll give that a try. I've been out of the c# world for a couple years. Has the updatepanel been deprecated by something better or are you not using it because it's unnecessary in dnn?
|
|
Coordinator
Jun 1, 2012 at 10:06 PM
|
Typically I just let DNN handle it. I do still have modules that use it, but I haven't had any web.config issues. Can you check to see if the modulename folder in your desktopmodules folder (in IIS) is configured as a Virtual Directory? It shouldn't be.
The template assumes you put the module into
/desktopmodules/modulename/ within your DNN website, are you by chance placing it elsewhere?
|
|
|
|
I actually have the similar issue using the newest template (v2.2).
I created a DAL2 module, but if I add any DNN control into the page, I will see:
"Element 'DNNGrid' is not a known element. This can occur if there is a compilation error in the Web site, or the web.config file is missing."
The module is able to compile without any issue, and the website is running correctly. Virtual Directory is also correct. I am not sure if I really need to add web.config into this module environment. Everything is still working fine, but just will see a lot green underline on the elements, and intellisense won't work for those DNN controls.
|
|
Coordinator
May 2 at 4:32 PM
|
You can't add a web.config to the module project or it will kill the DNN site.
|
|
|
|
**christoc wrote:**
You can't add a web.config to the module project or it will kill the DNN site.
Thanks, I figure the same. I guess I just have to run it without intellisense then.
|
|