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

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Left behind aspx.cs filesLeft behind aspx.cs files
Previous
 
Next
New Post
2/22/2017 2:09 PM
 
We've recently upgraded several DNN 7.4.2 installations to 8.0.4 and I've noticed that the upgrade process left behind all of the aspx.cs files in the folder structures.  I did some searching here and online but didn't find information on how to handle their removal.  I've used a merge/compare tool to look at a fresh DNN8 vs the DNN8 upgrade folder to see the differences of what aspx.cs files exist there that don't exist in a fresh installation.

What's the correct process of removing these files?  My plan was to install like modules into a fresh DNN8 install to then compare versus our upgraded DNN8 existing portals to see what's different.


Also question related to load order.  If the application has a DLL of the aspx.cs files does it just ignore them or does it actually load them?  I think one of our applications has modified aspx.cs files for custom features, if it ignores them what's the correct process to add back in those custom features?
 
New Post
2/22/2017 2:57 PM
 
DNN 8 moved to precompile the website, not only DNN library into a dll, therefore .ascx.cs files are no longer needed and used.
you may remove them or ignore them (though I would have preferred DNN to delete it).
For installed modules, it depends on the build process, whether it includes all the code behind files in its dll or reads it as separate files.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/24/2017 2:33 PM
 
Is there guidance on how to properly move our code changes from the aspx.cs into the precompiled version of DNN 8.x now?
 
New Post
2/24/2017 4:07 PM
 
if you use to modify source code of DNN, you would need to use Source version of DNN, which includes compiling website as well.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Left behind aspx.cs filesLeft behind aspx.cs files


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