Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0app_code issuesapp_code issues
Previous
 
Next
New Post
5/20/2007 12:53 PM
 

Hello All,

I am developing modules for version DNN434 in C#. I also use Visual Studio 2005 Pro Edition as the IDE running version 2.0.50727 of the .NET framework.

I have multiple directories under App_Code some of which are there because of the module wizard but others are ones I created as additional business logic to be used across the board.

So the issue is that I can't access all of the directories when I need to. It looks like it has something to do with the order in which they were defined in the web.config. I actually created a grid on my own and definitely saw a pattern. Let me illustrate:

<codeSubDirectories>
                <add directoryName="Folder 1"/>
                <add directoryName="Folder 2"/>
                <add directoryName="Folder 3"/>
                <add directoryName="Folder 4"/>
</codeSubDirectories>

Ok from the example above if I am in a source file within Folder 4 then I can utilize the "using" statement and access any of the other folders. But if I am in Folder 1 I can only access Folder 1 namespace. In Folder 2 I can access Folder 2 and Folder 1. And you can see the other permutations.

The bottom line is that you can access your own folder's namespace and those folders defined above you.

So is this a known bug in .NET? Is there a compilation attribute I can set? Or am I just misusing the App_Code folder? I really don't want to create separate projects or dlls for these individual files. I shold also be clear in that ALL the folders can be accessed in my /DesktopModules/ folder.

Any help would be greatly appreciated.

Thanks,

Allan

 

 
New Post
5/20/2007 1:56 PM
 

 if you didn't use the "using" statement and fully qualified the assembly does it work?

I have never tried to reference anything but the DotNetNuke.dll in any module (because you can't count on a module being installed). However, I do understand why you want this, because you want to share components.

This sounds like a ASP.NET compilation bug. If you have a assembly (a .dll) in the bin folder it will definatly work. For dynamic code it seems to be having a problem :(



Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
New Post
5/20/2007 2:37 PM
 

I took your advice and tried to just access objects by fully qualifying them but I still received the error. I also agree with you in that I think it is a compilation error within asp.net. I was just hoping someone in the forum here may have come across this same issue.

Still looking for a fix so would appreciate any help.

 

Thanks,

Allan

 
New Post
5/31/2007 2:05 PM
 

I have this same problem, but it definately seems DNN related as it works fine on version 4.0.2, but breaks on version 4.4.1.

Any / all help appreciated on this one!

Thanks,

Ian

 
New Post
5/31/2007 2:34 PM
 

One of the really strong arguments towards having a WAP and compile the DLL rather than leaving it for JIT compilation.  I have some modules that need to share components from other modules and because I have compiled them I can easily reference the DLL now.


-- Jon Seeley
DotNetNuke Modules
Custom DotNetNuke and .NET Development
http://www.seeleyware.com
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0app_code issuesapp_code issues


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out