Products

Solutions

Resources

Partners

Community

About

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

HomeHomeFuture Developm...Future Developm...DNN neXtDNN neXtIs the development branch on gituhub slightly broken?Is the development branch on gituhub slightly broken?
Previous
 
Next
New Post
7/30/2015 6:28 AM
 

I just brought my repository up to date with GitHub. 

I’m on the development branch and I’ve found that I cannot do a straightforward Release build.  It looks to me like there is a kerfuffle in some way related to Log4Net.  The last comment on Peter’s blog post indicates someone else had a problem here. (http://dnn-connect.org/community/blog...)

I located and manually built the DotNetNuke.Log4Net solution (it’s a separate solution – why is that?).

Even that was not really sufficient.  I found I needed three (maybe four) attempts at the Release build before it was completed.  Each attempt seemed to succeed with a few more projects.

Is it meant to be like this?  I’ve not built the source off GitHub for a while.  I don’t recall it being like this.


Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
7/30/2015 12:31 PM
 

I usually have to add some missing references whenever I checkout the branch. However the last time I did it, I think it compiled the first time. The odd thing is that when I reload the solution, VS would fix things by itself. Sometimes I had to reload a few times. 

 
New Post
7/31/2015 6:11 AM
 
log4net was added recently, so please make sure you're using the latest sln file . As to problems, I've seen the occasional issue when compiling in release mode, this seems to be related to some reorganisation that was done for the DCC module/API - the odd thing is that not everyone gets this, I believe it occurs in vs.net 2012 but not 2013/2015, so it's likely a timing issue. Typically if I get a failure when compiling in release, compiling in debug and then release works as expected - I do also get one other issue where petapoco.dll is not copied to the bin folder (I logged a jira) but so far it only seems to be me so it may be specific to my machine (where vs.net is borked and acting up i.e. intellisense sometimes fails etc.)

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeFuture Developm...Future Developm...DNN neXtDNN neXtIs the development branch on gituhub slightly broken?Is the development branch on gituhub slightly broken?


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