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

HomeHomeDevelopment and...Development and...Open Core Testi...Open Core Testi...Dynamic Content Type Manager brings up an empty DNN pageDynamic Content Type Manager brings up an empty DNN page
Previous
 
Next
New Post
9/30/2015 4:49 PM
 
cathal connolly wrote:

I find it very strange as we (the dev team) pretty much use the source build (and DNN_Platform.sln solution) exclusively (it's QA who make more use of the install/upgrade packages). I dont understand why you're seeing anything different, are you perhaps using an old (vs.net 2010/2012) version of visual studio?

Here's my standard process for working with source builds (many people automate these steps with powershell scripts but i'll show the manual steps)

1. I check out the branch I want from github

2. I execute the following commands to ensure a clean environment (which can be necessary when switched from 7.4.2 to 8.0.0 etc)

  • git reset --hard
  • git clean -dfx

3. I open vs.net 2013/2015 and open the DNN_Platform.sln solution

4 I change the drop-down to release and right-click the solution file at the top and do a "rebuild solution" (typically a build solution is fine for a "fresh" build but a little paranoia never hurts)

5. I hit localhost/dnn_platform and everything works

Note: if i'm debugging i'll change the web.config to use debug

As to the missing appSetting this is deliberate - Joe covered this in a recent blog http://www.dnnsoftware.com/community-blog/cid/155269/a-break-with-the-past , and i've ensured it was noted on the DNN 8 breaking changes wiki http://www.dnnsoftware.com/wiki/dnn-8-breaking-changes

 

Download the source from Codeplex and try it. I am doing nothing like what you have mentioned. No Github involved.

 
New Post
9/30/2015 4:54 PM
 
Brian Dukes wrote:
I'm going to guess that Tony didn't do a release build with his source package before doing the initial install (as it's a non-obvious step), and so the module packages weren't generated. I'm not sure what the best way is to make that more obvious, but, in my experience, it's a common stumbling block for people trying to get familiar with the source of DNN.

 

When you load DNN_Platform.sln into VS, it's already in release mode and I am able to compile it. Through Nuget it downloads and installs the necessary packages.  DNN wouldn't install and run if it doesn't compile. What I am talking about here is DNN runs already. The DCC manager doesn't show up. The conclusion was the Codeplex's source compiles fine but doesn't work right. The install package works fine.

 

 
New Post
10/10/2015 3:05 AM
 

I did a fresh install using DNN8 ctp6 source package and the DCC manager still doesn't show up. There are other admin options which also do not show up like the File Management and Taxonomy. Can someone verify this? I am not going to believe this happens only to me. 

 
Previous
 
Next
HomeHomeDevelopment and...Development and...Open Core Testi...Open Core Testi...Dynamic Content Type Manager brings up an empty DNN pageDynamic Content Type Manager brings up an empty DNN page


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