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.0Issue creating no-source deploymentIssue creating no-source deployment
Previous
 
Next
New Post
5/31/2006 10:00 AM
 
it is not possibel to publish a site at this time.  See this link for a worksround
http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/80/threadid/27731/scope/posts/Default.aspx

 
New Post
6/1/2006 12:58 AM
 
Thanks Bertcord, I knew I wasn't completely crazy.  Any idea on if this issue will be addressed in the core?  It seems like this prevents (in some cases) for the creation of No-Source deployments of modules in asp.net 2.0 which is one of the important requirements of the DNN 4 methodology.

Thanks
 
New Post
6/9/2006 6:05 AM
 
The problem can be solved quite easy. You have to replace the usercontrol in the .ascx file with a placeholder. In the code behind you have to load the with Page.LoadControl
and add the loaded control to placeholder controls collection.

Example ascx file:
<asp:Placeholder runat="server" id="phViewMyModule" />

Code Behind:
phViewMyModule.Controls.Add(Page.LoadControl("ViewMyModule.ascx"))
 
New Post
10/5/2006 3:40 PM
 

You described the problem extremely well.  I have the exact same problem with creating a form with a sub form on it and both are supposed to run withing DotNetNuke 4.3.5.

Apparently I saw some Microsoft articles that suggest dynamic registration and xml generation isn't happening so the parent form cannot connect with the child form correct.

Howver, in dynamic test mode it worked just fine using Visual Studio 2005 / Sql Server 2005.  It also compiled just fine using Publish Web.  The problem is when the private assembly is loaded for the parent form it does work with the same error message your are getting.  However, the child form works fine as a private assembly and running independantly.

Let me know if you find a solution.  It is sad to be done but you cannot deploy the private assembly.

Best regards


Kevin Donahoe CEO, Architect, and .Net Developer http://www.NewTechnologyAdvantage.com
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Issue creating no-source deploymentIssue creating no-source deployment


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