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...Why doesn't DNN ever just compile from the get go? (CTP5 included)Why doesn't DNN ever just compile from the get go? (CTP5 included)
Previous
 
Next
New Post
9/27/2015 10:37 PM
 

I can never open the source of DNN in Visual Studio and get it to compile right away. I used to spend a lot of time fixing the references of the projects to get it to compile eventually.

I tried to open CTP5 today and it froze my Visual Studio 2015 and got tens of thousands of errors! I killed VS and decided I wasn't going to spend a single second trying to get it to compile. This is very frustrating. Why can't DNN even compile correctly the first time?? I want to 'Rebuild Solution' and expect VS to restore the Nuget packages and compile fine. 

What does it take to make the DNN solution compile without a lot of user intervention? Why are there many broken references in the projects? 

I suppose I can try the Install file but why is the Source file always so broken?

View post on imgur.com

 

 

 

 
New Post
9/28/2015 2:28 AM
 
We are facing similiar issues ater migrating to Visual Studio 2015. Existing projects did not compile sucessfully - in Visual 2013 there is everything OK (the same code (!)).

I've done some research and manually add some missing references (there were some problems with System.Management classes). I was not able to fix errors in DotNetNuke.UnitTests (or something like that). Finally i excluded Unit test projects from solution. Now it is OK (rebuild all working) but this is just a workaround.

Any other member facing similar issues after migrating to Visual Studio 2015? I will check the exact projects name and write it down in this thread.
 
New Post
9/28/2015 7:54 AM
 
you must compile the solution first of all in "release" mode- this builds the various packages and ensures they are in place. You can then (optionally) build in "debug" mode (if you need to debug)

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
9/28/2015 1:16 PM
 

I am opening DNN_PlatformNoTests.sln. It doesn't compile either in debug or release modes. Then I found out that  DNN_Platform.sln compiles fine. It's already in release mode. So what's the deal with DNN_PlatformNoTests.sln? I have been using it in earlier DNN versions and it worked fine and lately it gives a gazillion errors.  I use it because I thought it's the same as DNN_Platform.sln without the test projects and so I don't have to worry about them if they don't compile. 

Expect users to be using the different solution files if you're including them in the archive file. 

I guess my lesson now is never open DNN_PlatformNoTests.sln.

 
New Post
9/28/2015 2:56 PM
 
we're aware DNN_PlatformNoTests.sln needs fixed - as it's a CTP that will be done by the final release.

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Open Core Testi...Open Core Testi...Why doesn't DNN ever just compile from the get go? (CTP5 included)Why doesn't DNN ever just compile from the get go? (CTP5 included)


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