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...PSA - Installing/Upgrading DNN v8.0.1 May Break Your SitePSA - Installing/Upgrading DNN v8.0.1 May Break Your Site
Previous
 
Next
New Post
3/18/2016 9:14 AM
 

PSA: Installing or upgrading DNN v.8.0.1 may break your website unless your server supports the ability to launch EXE files. This version automatically installs Microsoft.CodeDom.Providers.DotNetCompilerPlatform_01.00.01_Install.zip, which is a runtime compiler to support C# 6 and VB 14 files that are uncompiled. A workaround can be found at https://dnntracker.atlassian.net/brow....

OP/ED: I question the decision and lack of explanation by the team's leaders to release a version that is sure to break on nearly any hosting company. IMHO, this should have been an optional module to start, and its impact was curiously left out of the release notes other than to say that C# 6 and VB 14 are supported... a feature of little to known use that I am aware of in this particular release and not discussed in any meaningful way that I saw in DNN's blogs or the release notes.

What makes me most upset is that this version is the only known fix for critical issue 2016-04 (Critical) Potential CSRF issue on WebAPI POST requests on 3/16/2016, and creates the "Critical" tag above the DNN logo in the control panel. Installing this version will very likely break anyone's DNN website unless they have the ability to affect changes at the machine level, which is IMHO not going to be the case across the majority of installations on a shared server.

The workaround will help correct the automatic installation of CodeDom on a site after it has been upgraded, but the release ZIPs have not been updated on CodePlex and there is not special mention in the release notes as a warning. As more people respond to the critical issue, they will find this out the hard way and I believe it will reflect poorly on the project. It is not making easy work of managing a large number of websites across different hosting companies where the ability to run EXEs would have to first be tested.

Thank you to all the hard working and dedicated members of the DNN team. I am a loyal developer and advocate for DNN, and think that communication could have been better and the move to implement CodeDom should have at least started out as optional.

 
New Post
3/18/2016 10:02 AM
 
you may remove the package from /install/module subfolder, prior to launching the upgrade.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
3/18/2016 10:07 AM
 
Thanks, Sebastian! I haven't tried that myself, but that is another nice workaround that the community should know about. I wasn't sure if it was needed in other parts of the CMS or the install/upgrade routine though.
 
New Post
3/18/2016 11:12 AM
 
that's the easiest option - in this case, the module won't be installed and web.config not touched.

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...PSA - Installing/Upgrading DNN v8.0.1 May Break Your SitePSA - Installing/Upgrading DNN v8.0.1 May Break Your Site


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