Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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...SRC packages for BETA1 brokenSRC packages for BETA1 broken
Previous
 
Next
New Post
1/4/2016 7:10 PM
 
Patrik Johansson


Joined: 8/5/2004
Posts: 333

Joe,

Thank you for taking the time to responding to this and for making a video also, much appreciated.

DNN_PlatformNoTests.sln  generates a lot of errors in both Debug and Release mode. Only way I know to get it to work is to first open the DNN_Platform.sln, build that, and then open the DNN_PlatformNoTests.sln which will then work. The DNN_Platform.sln however seem to work much better with DNN 8 than with previous DNN version which usually was quite a hazel to get working as witnessed by numerous posts to that matter. I also had no build problems with DNN_Platform.sln in neither DEBUG nor RELEASE mode.

About InstallWizard.aspx you are right and I'm wrong, it is indeed included in the SRC package although not in the expected place but it gets placed where it should after first build, just as you show in your video.

 I notice that DNN8 is setup to use IISEXPRESS rather than "big" IIS,which is a nice change but you don't seem to use that but instead setup a new virtual directory in IIS, why is this and could it have anything to to with the problems I've had when trying to run DNN8 by using "run" in Visual Studio 2015? I also noted that in the video you don't seem to rename any of the release/development config files to web.config, but I also noticed that a web.config is now created during build which seem to be a copy of release.config, is this a new behavior in DNN8?

Edit:

Also, how come you set the DB name first when that is supposed to be configurable via the InstallWizard? Is that perhaps something that isn't working fully in DNN8 yet?

 
New Post
1/4/2016 8:42 PM
 
Patrik Johansson


Joined: 8/5/2004
Posts: 333
Good news, after first setting the connection string manually in web.config, the InstallationWizard seemed to start working again. Which is of course somewhat ironic considering that you normally set the connection string in the InstallationWizard. Having done that, it seems like DNN Beta 1 is now working both in IIS and IISEXPRESS, although I haven't really put it through some heavy testing yet.
 
New Post
1/13/2016 9:31 AM
 
Patrik Johansson


Joined: 8/5/2004
Posts: 333

The RC1 version seem to have the same problem as the BETA, that the installation Wizard won't kick in unless you specify the connection string in web.config in advance. This would probably be something that needs fixing before the actual release.

Also, when trying to see the installation log after the install wizard has completed you only get "No Installation Log" when you click the "see installation log button"

 
New Post
1/13/2016 10:49 AM
 
Joe Brinkman


Joe Brinkman's Avatar

blog.theaccidentalgeek.com
Joined: 5/18/2003
Posts: 2356

Patrik,

  Please log a bug in Jira on the specific issues you are seeing in the DNN_PlatformNoTests.sln.  I have not personally tested this solution so I am sure you are seeing legitimate bugs in that area since the team primarily develops with the main solution.

IISExpress is something new that was only really possible once we converted the website to use Web Application Project (WAP).  I have a number of PowerShell scripts that I use for installation and configuration of most of my environment and have been doing things a certain way for 10 years.  I also prefer IIS because I can run the website without starting up Visual Studio or any other tools.  I do a lot more demo/test scenarios than I do pure dev work so for me IIS is a better choice.

 As for release/development.config getting copied to web.config - that is something we have been doing for at least the last five or six years.  Often we organize files so there is the least possibility for a failure to result in data loss.  For example, if you have a web.config in the root project and you build the DNN Upgrade package, you have to explicitly remember to remove the web.config as part of the build.  If you fail to do so, you can overwrite someones web.config and cause them to lose a machinekey which would completely kill all the user accounts (the hashing algorithm for passwords depends on machinekey).  Conversely, if you forget to copy release/development.config to web.config in the case of a new Install build package, this is an easily recoverable issue and one that is quickly identified in QA.

As for the DB name - I do that because I don't have SQL express installed.  I run with full SQL Server.  There is some configuration issue on my machine which means that when DNN doesn't find SQLExpress in the default install, it gives me an error rather than showing the InstallWizard.  Other people don't have this problem and I have not taken the time to track down the root cause.  Since I mostly do installs from PowerShell, it is not something I normally have to deal with.

Joe Brinkman
DNN Corp.
 
New Post
1/13/2016 2:42 PM
 
Tony Henrich


Joined: 12/15/2008
Posts: 838
Joe Brinkman wrote:

Patrik,

  I have gone through the beta package from CodePlex and it is working exactly as expected.  The biggest problem for most people trying to build DNN from source is that they don't understand how the source is organized or how our build process works.  We often copy files to different directories during the build process to get around some issues with ASP.Net and Visual Studio.  For example, to minimize security risks, DNN will delete the Install Wizard after the installation is complete.  In the development environment this results in Git thinking that want to delete the file and can result in someone inadvertently checking in the deletion into GitHub.  To avoid this, we keep the install wizard in a separate location and copy it into the Install folder during the build process.  Since it gets deleted on install, the net result is that Git is happy and we don't worry about someone accidentally checking in a delete.

The other major issue is that most people don't do "Release" build before attempting to install.  The release build is critical for us since that is the build where we package up all the modules which are needed during install.  Typically I will do a debug build to generate the PDBs and to create a debug version of the web.  When that is done, I will do a release build to create all the various module packages.  Once that is done I am free to run the actual installation.

 I have a short (~8 min) video (no audio) which shows you the full process using the DNN 8 Beta source package from CodePlex. https://www.youtube.com/watch?v=mAUvQ...

 Note:  As DNN 8 uses C# 6.0 constructs in a number of locations you will need to use Visual Studio 2015 to compile DNN.

 

I don't know what you mean by "most people don't do "Release" build before attempting to install". When you open a .NET solution in Visual Studio, it opens in the configuration it was last saved in.  The DNN source is saved in Release configuration already (Codeplex or Github. I think they are the same) which means if I build the solution it will build in release mode and everything gets built and when I run the solution after it compiles without errors, it will go through the first time installation during the first run. We don't have to do anything to build in release mode. Works fine. I don't need to manually tweak anything. It will also download the missing nuget packages. Although I think I have to reopen the solution for the references to work properly.

For the longest time, the DNN source was a pain for me to build every I downloaded it. I think the DNN source used to be in debug configuration which caused all kinds of problems. The best way now is to download it only once and use Github's pull requests to get the latest changes periodically.
 
 Page 2 of 3
Previous123Next 
Previous
 
Next
HomeHomeDevelopment and...Development and...Open Core Testi...Open Core Testi...SRC packages for BETA1 brokenSRC packages for BETA1 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