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...Upgrade compilation error from 5.2 to 5.3 Any answers?Upgrade compilation error from 5.2 to 5.3 Any answers?
Previous
 
Next
New Post
3/18/2010 10:14 AM
 

I should have read the notes on the release at codeplex:

Due to potential namespace ambiguities between System.Web, DotNetNuke.Web and Telerik.Web namespaces in DotNetNuke 5.3.0 you may encounter the following error during upgrade: “Type 'Web.HttpResponse' is not defined.” This error primarily occurs if an the XML module is already installed. It is recommended that you uninstall the XML module if it is not in use. We anticipate releasing a patched version of the XML module this week to address this issue.

U restore my back ups, then remove the XML fiel and I sucessfully upgraded my instalations.

 
New Post
3/18/2010 10:19 AM
 

So my upgrades work fine, but in one of my installations when I click on the Search Engine Site map, I get the following error:

ModuleId: 554
ModuleDefId: 155
FriendlyName: Search Engine Sitemap
ModuleControlSource: DesktopModules/Admin/Sitemap/SitemapSettings.ascx
AssemblyVersion: 5.3.0
PortalID: 0
PortalName: *** Test
UserID: 1
UserName: *****
ActiveTabID: 132
ActiveTabName: Search Engine Sitemap
RawURL: /Admin/SearchEngineSitemap.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://home.esghr.com/Admin/Taxonomy.aspx
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 GTBDFff GTB7.0
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: b04158bf-84df-425c-8e3e-77a5adc749fc
InnerException: C:\Internet\Websites\DotNetNuke\DesktopModules\Admin\Sitemap\SitemapSettings.ascx.vb(230): error BC30389: 'p' is not accessible in this context because it is 'Friend'.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.Compilation.BuildManager.CompileWebFile
StackTrace:
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: C:\Internet\Websites\DotNetNuke\DesktopModules\Admin\Sitemap\SitemapSettings.ascx.vb(230): error BC30389: 'p' is not accessible in this context because it is 'Friend'. ---> System.Web.HttpCompileException: C:\Internet\Websites\DotNetNuke\DesktopModules\Admin\Sitemap\SitemapSettings.ascx.vb(230): error BC30389: 'p' is not accessible in this context because it is 'Friend'. at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc) at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace ---
Source:
Server Name: ****

The rest of the Taxonomy part is working fine. Any ideas?

 
New Post
3/25/2010 5:32 PM
 
Thanks Kenneth. Mildly embarrassing that the DNN crew would commit such a junior error: either fully qualify or don't qualify at all.
 
New Post
3/29/2010 8:55 PM
 

I am getting the same error in the search engine site map, anyone find a fix yet?

 
New Post
3/29/2010 10:08 PM
 
Dave Scheffer wrote:
Thanks Kenneth. Mildly embarrassing that the DNN crew would commit such a junior error: either fully qualify or don't qualify at all.
It's the bane of abbreviations - which fail as soon as the context scope mutates.

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...Upgrade compilation error from 5.2 to 5.3 Any answers?Upgrade compilation error from 5.2 to 5.3 Any answers?


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