Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...VB source files in Install versions ?VB source files in Install versions ?
Previous
 
Next
New Post
7/13/2009 10:44 AM
 
Allan Williams


Joined: 10/13/2007
Posts: 252

I have a question from a client and I'm not sure how to answer it.  They understand that DNN is a compiled web application and that all the core DLL's are in the bin and bin/Providers folders.  The question they have is for a compiled web application, why are there vb source files in the Admin subfolders? 

 I have wondered about that myself and haven't really worried about it.  But my client wants an explanation - any assistance would be appreciated.
 
New Post
7/13/2009 11:53 AM
 
Ian Lackey

Joined: 7/22/2006
Posts: 127

The vb files are the code-behind files for the aspx & ascx files for the site. There might also be a few in App_Code as well. This is because, while the core library is built in class library project and therefor compiled, the actual website is built using the website project type and not the Web Application project type. Web applications always precompile all of the source code for aspx, ascx & app_code files; however websites do not. There is an option to precompile sites using the publish method of a site if you must have the site precompiled. However, the last time I looked into it, DNN has an issue with being precompiled as it is not designed to be.

With all of that said, may I ask why the concern about the source files? Precompling a website only give a small performance boast on the first request after the site is reloaded. So unless performance is a HUGE concern it is generally not worth the trouble.

Just FYI here is an older thread regarding precompiling: http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/78/threadid/27731/scope/posts/threadpage/5/Default.aspx
 
New Post
7/13/2009 12:04 PM
 
Allan Williams


Joined: 10/13/2007
Posts: 252

Thnaks for the explanation.  I understand that the vb files are the code-behind files.  I guess the quesiton is why is some of DNN precompiled (i.e. all the DotNetNuke dll's in the bin folder) and why is some of it not (i.e. all the vb files in the Admin sub-folders).  

I'm not suggesting it's good, bad or otherwise ... I just want to explain to my client the reason for this and also why having the vb files in the Admin sub-folders poses no security risks...
 
New Post
7/13/2009 2:01 PM
 
Ian Lackey

Joined: 7/22/2006
Posts: 127

 

The easiest way I can explain is that the dll files in the bin represent particular pieces of the core framework and are separated for easier maintainability of the core, and therefore are compiled individually. The site itself has no need to be precompiled based on the design of the framework, so it is not.
As for security ricks, there really is no difference between having precompiled and "Just In Time" compiled code on the server. The code of either is just as easily accessible to anyone with access to the server.
With that said, NO ONE except the server administrators should actually have access to these code files. A typical internet user (or hacker for that matter) can access the source code (compiled or not) unless they have access to browse the server's file system. If that is the case, you have much bigger issues than exposing your code. On that note, DNN is open source so if someone wants to see what your code looks like they can just go to CodePlex and browse the source or download the entire framework. ;)
 
Bottom line: There is no security in "hiding" the source code of your application. The term for that is "Security through Obscurity" and everyone in the security community believe that it offers no security at all.
 
 Page 1 of 1
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...VB source files in Install versions ?VB source files in Install versions ?


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