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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...We should have a subforum under  Future Development for the next versionWe should have a subforum under Future Development for the next version
Previous
 
Next
New Post
5/3/2015 2:09 AM
 

There's a subforum under 'Future Development' forum for the MVC version. We also need one for the next version 8.0. I have tried multiple tiems to download the 8.0 branch from gitbub and it doesn't compile. I have spent time to get it to compile and it finally did but it gave a fatal error upon installation. I opened a ticket about this in the tracker but no progress so far.

The subforum would add more transparency about the development and issues encountered.

Some developers from dnnsoftware are working on 8.0 so the solution must be compiling and working for them. It would be helpful if they upload a working compilable version on github so we can check it out. dnnsoftware is asking for help from the community but they are not making it easy for us to do this if the thing doesn't work! I also asked more than 2 weeks ago about the support for MVC partial views and received no answer. All this friction is discouraging and not helpful. Or maybe I should wait till this version is mature and out.

 

 
New Post
5/3/2015 9:16 AM
 

I agree about the forum, I'm sure we will create one at the appropriate time, right now the "core forum alpha and beta" forum is the best for pre-release questions - http://www.dnnsoftware.com/forums/for...

As to the 8.0.0 item failing to build, we fixed that the other day, and then broke it yesterday (now fixed, apart from the unit tests AFAIK) - that's simply what happens in the early days of pre-release build. We are planning a new CTP, and the code will start to get more stable in the next few weeks. As to the MVC question, I don't believe that's supported, but will ask


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
5/3/2015 2:28 PM
 
I just checked out the branch and it doesn't compile. 261 errors. It NEVER compiled for me and I have checked it out at different occasions after different updates. I really do not wish to spend lots of time getting it to compile every time I do a clean checkout.

What does it take to checkout the whole branch and get it to compile without manual intervention? Unless I am doing something wrong, how are you getting it to compile? I suggest you test this on a clean machine without any kind of pre setups for the benefit of the rest of us.
 
New Post
5/3/2015 4:58 PM
 
if you gave an example of the errors it might help - note, you do need .net 4.5, and it requires vs.net 2013 or above

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
5/3/2015 8:31 PM
 
Yes I am aware of all that. A Visual Studio version prior to 2013 is not going to be able to open a VS 2013 solution/project and the .NET target is already defined in the project file.

I am going to fix the references one more time and post the issues after that.

Here's a sample:

Error 149 The type or namespace name 'Web' does not exist in the namespace 'DotNetNuke' (are you missing an assembly reference?) UI\WebControls\PropertyEditor\Edit Controls\DNN Edit Controls\DNNRegionEditControl.cs 29 18 DotNetNuke.Library
Error 152 The type or namespace name 'Web' does not exist in the namespace 'DotNetNuke' (are you missing an assembly reference?) UI\WebControls\PropertyEditor\PropertyLabelControl.cs 34 18 DotNetNuke.Library
Error 156 The type or namespace name 'Web' does not exist in the namespace 'DotNetNuke' (are you missing an assembly reference?) Entities\Controllers\HostController.cs 40 18 DotNetNuke.Library
Error 53 The type or namespace name 'Web' could not be found (are you missing a using directive or an assembly reference?) Entities\Host\Host.cs 45 11 DotNetNuke.Library
Error 127 The type or namespace name 'Web' could not be found (are you missing a using directive or an assembly reference?) UI\Containers\Container.cs 54 11 DotNetNuke.Library
Error 263 The type or namespace name 'OpmlOutlines' could not be found (are you missing a using directive or an assembly reference?) WebControls\FeedBrowser.cs 265 67 DotNetNuke.Library
Error 264 The type or namespace name 'OpmlOutlines' could not be found (are you missing a using directive or an assembly reference?) WebControls\FeedBrowser.cs 304 62 DotNetNuke.Library
Error 265 The type or namespace name 'OpmlOutlines' could not be found (are you missing a using directive or an assembly reference?) WebControls\FeedBrowser.cs 350 42 DotNetNuke.Library
Error 266 The type or namespace name 'OpmlOutlines' could not be found (are you missing a using directive or an assembly reference?) WebControls\FeedBrowser.cs 395 44 DotNetNuke.Library
Error 262 The type or namespace name 'Opml' could not be found (are you missing a using directive or an assembly reference?) WebControls\FeedBrowser.cs 254 17 DotNetNuke.Library
Error 21 The type or namespace name 'Instrumentation' does not exist in the namespace 'DotNetNuke' (are you missing an assembly reference?) Common\Globals.cs 60 18 DotNetNuke.Library
Error 22 The type or namespace name 'Instrumentation' does not exist in the namespace 'DotNetNuke' (are you missing an assembly reference?) Common\Initialize.cs 39 18 DotNetNuke.Library
Error 23 The type or namespace name 'Instrumentation' does not exist in the namespace 'DotNetNuke' (are you missing an assembly reference?) Common\Internal\ServicesRoutingManager.cs 23 18 DotNetNuke.Library
Error 24 The type or namespace name 'Instrumentation' does not exist in the namespace 'DotNetNuke' (are you missing an assembly reference?) Common\Lists\ListEntryCollection.cs 27 18 DotNetNuke.Library
Error 25 The type or namespace name 'Instrumentation' does not exist in the namespace 'DotNetNuke' (are you missing an assembly reference?) Common\Lists\ListInfoCollection.cs 26 18 DotNetNuke.Library
Error 26 The type or namespace name 'Instrumentation' does not exist in the namespace 'DotNetNuke' (are you missing an assembly reference?) Common\Utilities\Config.cs 31 18 DotNetNuke.Library
Error 27 The type or namespace name 'Instrumentation' does not exist in the namespace 'DotNetNuke' (are you missing an assembly reference?) Common\Utilities\DataCache.cs 33 18 DotNetNuke.Library
Error 28 The type or namespace name 'Instrumentation' does not exist in the namespace 'DotNetNuke' (are you missing an assembly reference?) Common\Utilities\FileSystemUtils.cs 38 18 DotNetNuke.Library
Error 29 The type or namespace name 'Instrumentation' does not exist in the namespace 'DotNetNuke' (are you missing an assembly reference?) Common\Utilities\RetryableAction.cs 24 18 DotNetNuke.Library
Error 30 The type or namespace name 'Instrumentation' does not exist in the namespace 'DotNetNuke' (are you missing an assembly reference?) Common\Utilities\XmlUtils.cs 40 18 DotNetNuke.Library
Error 31 The type or namespace name 'Instrumentation' does not exist in the namespace 'DotNetNuke' (are you missing an assembly reference?) Data\SqlDataProvider.cs 36 18 DotNetNuke.Library
Error 32 The type or namespace name 'Instrumentation' does not exist in the namespace 'DotNetNuke' (are you missing an assembly reference?) Entities\Content\AttachmentController.cs 29 18 DotNetNuke.Library
Error 33 The type or namespace name 'Instrumentation' does not exist in the namespace 'DotNetNuke' (are you missing an assembly reference?) Entities\IPFilter\IPFilterController.cs 37 18 DotNetNuke.Library
Error 34 The type or namespace name 'Instrumentation' does not exist in the namespace 'DotNetNuke' (are you missing an assembly reference?) Entities\IPFilter\IPFilterInfo.cs 32 18 DotNetNuke.Library
Error 35 The type or namespace name 'Instrumentation' does not exist in the namespace 'DotNetNuke' (are you missing an assembly reference?) Entities\Tabs\TabVersions\TabVersionBuilder.cs 32 18 DotNetNuke.Library
Error 36 The type or namespace name 'Instrumentation' does not exist in the namespace 'DotNetNuke' (are you missing an assembly reference?) Entities\Tabs\TabWorkflowTracker.cs 29 18 DotNetNuke.Library
Error 37 The type or namespace name 'Instrumentation' does not exist in the namespace 'DotNetNuke' (are you missing an assembly reference?) Common\Internal\EventHandlersContainer.cs 28 18 DotNetNuke.Library
Error 38 The type or namespace name 'Instrumentation' does not exist in the namespace 'DotNetNuke' (are you missing an assembly reference?) Entities\Modules\ModuleController.cs 47 18 DotNetNuke.Library
Error 39 The type or namespace name 'Instrumentation' does not exist in the namespace 'DotNetNuke' (are you missing an assembly reference?) Obsolete\LogController.cs 42 18 DotNetNuke.Library
Error 40 The type or namespace name 'Instrumentation' does not exist in the namespace 'DotNetNuke' (are you missing an assembly reference?) Services\Log\EventLog\LogController.cs 42 18 DotNetNuke.Library
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...We should have a subforum under  Future Development for the next versionWe should have a subforum under Future Development for the next version


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