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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...No Source CodeNo Source Code
Previous
 
Next
New Post
1/22/2008 3:40 PM
 

Hi all!!  we are using a new IT vendor and we're told that old vendor "lost" the sourcecode to huge application we use to build sites for our clients.  My first question is, can sourcecode be lost?  my understanding of dotnetnuke is that the sourcecode for the modules is stored in the SQL server tables.  is this true and if so how do we access that code?  I would also like to know if, without access to sourcecode we could create a testing environment?  I have fa few ideas on how to do this: by making a cc of the the whole application and the associated db, deleting all participant data and adding in "test" data to a few of the sites or testing at the site level only on a site created specifically for testing... is that possible without sourcecode or am I way off base? The problem we are having is that new modules or updates are being forced in the application and causing a lot of problems to the live site. Please help me understand...

 
New Post
1/22/2008 4:07 PM
 

Val,

Source code can absolutely be "lost".  But first, to understand that, I need to make clear that source code for a module is not stored in the database.  Source code for a DotNetNuke module generally resides in the form of a Visual Studio project as text files and is compiled into an assembly (dll) (although there are other permutations). What the developer in your case probably lost  was access to the files that created the assembly you are using.

You can create a test environment by making a backup of both the filesystem and database and restoring to a new server. You do not need the source code to re-create what you currently have in a different environment.

You will need to back up the whole web application solution and copy that to your new server. Set up a new virtual directory so that you can access the web application (point it to your newly copied file system).  You will then need to configure the SiteSqlServer key in the web.config file to point to a new copy of your database which you restored to a new instance of SQL Server.

Hope that helps,

Ian


Software Engineer
Co-Founder, dnnGallery
Stack Overflow: Ian Robinson
Twitter: @irobinson
Linked In: Ian Robinson
 
New Post
1/22/2008 4:17 PM
 

Thank you so much Ian for that explanation... that makes sense.  Could the web.config file have been a part of the source code? or do they definitely have access to that file.

 
New Post
1/22/2008 5:17 PM
 

Also, if this is a Dotnetnuke system, you really need to get support from a DNN specialist. Anyone not specifically familiar with the application and the DNN scene in general is really of very little value.

Rob

 
New Post
1/23/2008 10:43 AM
 

tigerlily,

The web.config is an essential piece of the application. You cannot have a functioning DotNetNuke site without it. Being that you could certainly have a DotNetNuke site without any custom or third party modules installed, and you still have a web.config -- it is not necessarily part of the "source code" for any one module. However, it does hold various keys and settings for modules to use (such as the credentials to access the database).  So think of it as a repository for application level settings that a custom module could use if so desired. With that said, in the case of DotNetNuke modules that Engage Software sells commercially we tend to avoid putting any setings in the web.config.  Having settings there can certainly increase the complexity of module installation and maintenance.

Hope that helps!

Take care,

Ian


Software Engineer
Co-Founder, dnnGallery
Stack Overflow: Ian Robinson
Twitter: @irobinson
Linked In: Ian Robinson
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...No Source CodeNo Source Code


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