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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Compiler errrors in Web Deployment Project for DNN 4.4.1Compiler errrors in Web Deployment Project for DNN 4.4.1
Previous
 
Next
New Post
2/15/2007 10:07 PM
 

I am using "Publish Web Site" option to deploy DNN Web Site with Allow this precompiled site to be updatable ticked and other defaults which merges each folder output to its own assembly. 
On run-time I've got error:
 The base class includes the field 'ctlRoles', but its type (DotNetNuke.Modules.Admin.Security.SecurityRoles) is not compatible with the type of control (ASP.admin_security_securityroles_ascx) , that discussed in this thread.


I decided to use   Web Deployment Project with options Allow this precompiled site to be updatable unticked,
Output Assemblies/Merge each folder output to its own assembly   - ticked. to get thesimilar errors  during compilation, not during run-time.
It gave me a lot of compile error, mostly related to Providers\HtmlEditorProviders\Ftb3HtmlEditorProvider\ftb3 folder, e.g.

Error 1 'InitializeCulture' is not a member of 'ASP.providers_htmleditorproviders_ftb3htmleditorprovider_ftb3_ftb_createlink_aspx'. C:\FSDNN\Providers\HtmlEditorProviders\Ftb3HtmlEditorProvider\ftb3\ftb.createlink.aspx 1 1 FSDNN_deploy
Error 73 'AddWrappedFileDependencies' is not a member of 'ASP.providers_htmleditorproviders_ftb3htmleditorprovider_ftb3_ftb_insertsmiley_aspx'. C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\fsdnn\af85da85\fba2fc8\App_Web_9ejuthkb.2.vb 476 1 FSDNN_deploy.

I didn't analyze the errors, but it could be potential problems related to them.
I beleive that DNN development team should do the Web Deployment build and clean all related errors before each release.


 


Michael Freidgeim http://geekswithblogs.net/mnf
 
New Post
2/21/2007 12:53 AM
 

I am having this same issue with a module I basically rewrote using the "Blank Module" solution. 

Apparently, this only happens when I install the PA into a clean "Source" version of DNN 4.4.1.
Installing into the DNN 4.4.1 "Install" version, and the module works fine.

It should be trying to access MyCompany.Module...but instead it is looking for "ASP.Desktopmodules_foldername_filename_ascx".

 

 
New Post
2/21/2007 7:15 AM
 

After further investigation, the module was failing on a source version of 4.3.7.14114

Production was 4.4.1.26939
Staging that failed was 4.4.0.28454
Staging that worked was 4.4.1.26939

Recompiling by referencing the 4.3.7.14114 dll fixed my problem on the production box.  I do have "Specific Version" set to false in both module and SQLDataprovider projects.

Not that it matters at the moment, but I'm curious if I code a module in a dev-environment of the 4.4.1.26939 latest DNN version...is this issue going to reappear if the module is installed to earlier DNN 4.x versions?

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Compiler errrors in Web Deployment Project for DNN 4.4.1Compiler errrors in Web Deployment Project for DNN 4.4.1


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