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

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