I make a branch from release 9.3.2 (in Visual Studio from GitHub) and when I build in release mode I get more error from packager from these project (Dnn.AuthServices.Jwt, DotNetNuke.Authentication.Facebook, DotNetNuke.Authentication.Google, DotNetNuke.Authentication.LiveConnect, DotNetNuke.Authentication.Twitter, DotNetNuke.Modules.CoreMessaging, DotNetNuke.Modules.DDRMenu, .......). The errors are always the same:
Errore errore imprevisto dell'attività "ExtensionPackager". System.NullReferenceException: Riferimento a un oggetto non impostato su un'istanza di oggetto. in DotNetNuke.MSBuild.Tasks.ExtensionPackager.b__0(XElement package) in System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext() in DotNetNuke.MSBuild.Tasks.ExtensionPackager.Execute() in Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute() in Microsoft.Build.BackEnd.TaskBuilder.d__26.MoveNext() Dnn.AuthServices.Jwt
I tried with Visual Studio 2015 and 2017, but I had same errors. Do you have any idea?
Thanks
I have install packages with
PM> .\build.ps1
and now compile in release mode (without fake error... probabily due msbuilb not found files in directories WebSite/Install/Module).
The previous release 9.0.0.0 build in release mode without that command.
Posted By Joe Craig on 25 Aug 2019 03:44 PM Usually you do not need to rebuild DNN. Do you have a use case that requires it? If not, perhaps some details as to why you did this can help us understand that you really are trying to do.
I think it's worth reiterating what Joe said. Building the DNN source code is really only necessary if you're either (1) going to work on and submit a pull request to GitHub to resolve an issue, or (2) you're forking the DNN code for some reason.
The latter almost always can instead be resolved using an extension point, API endpoint, or a pull request instead. Core code changes should be avoided at all costs. :)
Good luck and happy DNN-ing! :)
These Forums are dedicated to the discussion of DNN Platform.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.