Products

Solutions

Learn More

Partners

Community

Blog

About

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

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesAfter Upgrade, Building my project Breaks my DNNAfter Upgrade, Building my project Breaks my DNN
Previous
 
Next
New Post
11/11/2015 6:56 AM
 

Just upgraded Prod and Dev environments to DNN 7.4.2

Now when I build or run my Visual Studio project, my local DNN instance breaks. Visiting any page give the following error. This error can only be resolved by redeploying the upgrade package for 7.4.2 over the top of the site.

Obviously something important is being overwritten, but no idea what it might be. Any pointers?

Server Error in '/' Application.

Compilation Error

Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately. 

Compiler Error Message: CS0103: The name 'CanonicalLinkUrl' does not exist in the current context

Source Error:

Line 725:                        primaryHttpAlias = PortalSettings.DefaultPortalAlias;
Line 726:                }
Line 727:                if (primaryHttpAlias != null && string.IsNullOrEmpty(CanonicalLinkUrl))//a primary http alias was identified
Line 728:                {
Line 729:                    var originalurl = Context.Items["UrlRewrite:OriginalUrl"].ToString();


Source File: c:\LocalWebsites\dnn\Default.aspx.cs    Line: 727 

...snip...

            
Microsoft (R) Visual C# Compiler version 4.6.0079.0

for C# 5
Copyright (C) Microsoft Corporation. All rights reserved.



This compiler is provided as part of the Microsoft (R) .NET Framework, but only supports language versions up to C# 5, which is no longer the latest version. For compilers that support newer versions of the C# programming language, see http://go.microsoft.com/fwlink/?LinkID=533240

c:\LocalWebsites\dnn\Default.aspx(23,59): warning CS0108: 'DotNetNuke.Framework.DefaultPage.Form' hides inherited member 'System.Web.UI.Page.Form'. Use the new keyword if hiding was intended.
c:\Windows\Microsoft.NET\assembly\GAC_64\System.Web\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.dll: (Location of symbol related to previous warning)
c:\LocalWebsites\dnn\ErrorPage.aspx(12,63): warning CS0108: 'DotNetNuke.Services.Exceptions.ErrorPage.Form' hides inherited member 'System.Web.UI.Page.Form'. Use the new keyword if hiding was intended.
c:\Windows\Microsoft.NET\assembly\GAC_64\System.Web\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.dll: (Location of symbol related to previous warning)
c:\LocalWebsites\dnn\Default.aspx.cs(727,70): error CS0103: The name 'CanonicalLinkUrl' does not exist in the current context
c:\LocalWebsites\dnn\Default.aspx.cs(730,21): error CS0103: The name 'CanonicalLinkUrl' does not exist in the current context
c:\LocalWebsites\dnn\Default.aspx.cs(830,83): error CS0103: The name 'HeaderIsWritten' does not exist in the current context
c:\LocalWebsites\dnn\Default.aspx.cs(835,36): error CS0103: The name 'CanonicalLinkUrl' does not exist in the current context
c:\LocalWebsites\dnn\Default.aspx.cs(839,26): error CS0103: The name 'CanonicalLinkUrl' does not exist in the current context
 
New Post
11/11/2015 7:16 AM
 
OK, I found that there were a bunch of DotNetNuke dlls in my home\DesktopModules\bin folder that were being copied on build into home\bin and replacing the newer ones.

Actually, not sure WHY I have a bin folder under DesktopModules. Is that normal?
 
New Post
9/26/2016 4:05 PM
 
thanks for sharing this. I had a similar issue. My error was:

CS0103: The name 'HeaderIsWritten' does not exist in the current context

dotnetnuke.dll was getting overwritten with an older version during build.

"if the only tool you have is a hammer you tend to see every problem as a nail" http://www.carawaydesign.com
 
New Post
10/18/2016 4:33 PM
 

To answer the question if having a bin folder in your DesktopModules folder is normal the answer is no. I however have tried keeping copies of dll's to share in a separate folder and those accidentally over wrote dll's in the main site bin. Is it possible that your module is referencing the dll's from the wrong bin folder? I've had that happen and it can be tricky to figure out what causes it. Glad you figured out your issue though.

 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesAfter Upgrade, Building my project Breaks my DNNAfter Upgrade, Building my project Breaks my DNN


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.
DNN Launch Webinar
REGISTER NOW
DNN Launch Webinar
REGISTER NOW
DNN Launch Webinar
REGISTER NOW