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
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Building DNN 8 with VS 2017 apparently causing source install issuesBuilding DNN 8 with VS 2017 apparently causing source install issues
Previous
 
Next
New Post
5/6/2017 7:37 PM
 
Michael Durthaler


Joined: 9/18/2006
Posts: 308

I am not sure that Visual Studio 2017 is the issue but the procedure at this link http://www.dnnsoftware.com/answers/how-to-install-dnn-8-source-package states to build the dnn platform solution with VS 2015.  Chris Patera's note in the post is that DNN 8 or later must use VS 2015.

I was able to build the solution after handling the error that the CE version of SQL Server wasn't referenced.  This was preventing the DNN Tests DLL from installing as it was missing during the build.

Here is the procedure from the post:

1. After up zip the download, look for dnn_platform.sln file and open it with vs 2015. Run VS with administrator privilege. 

2. Build the solution. 

3. It will prompt the install screen to enter host password and database connection string. 

Mike D -- This didn't happen.  I got no errors but did try browsing directly.   Browsed to the site with IIS, from a web browser (chrome) and from VS 2017.  None of the methods got the install process running.  When I do try to browse I get this error:


Note -- I have installed the Install version and it runs just fine.  I have a separate database for the install and source versions.  The source is DNN8_DEV_SOURCE and the one for install has a totally different name.

4. From the person responding to the post: "My machine has windows 10, IIS, SQL 2012 and VS 2015."  Mike D -- I have Windows 10 Pro, SQL Server 2016 Express, SSMS 17, VS 2017, IIS 10.

OK -- Is VS 2017 the culprit?  If I have to I can use my work MSDN subscription to download 2015 and build with it instead.

Thanks for any help.

Mike Durthaler
 
New Post
5/7/2017 8:57 PM
Accepted Answer 
Michael Durthaler


Joined: 9/18/2006
Posts: 308

Resolved.

There is not a way around using VS 2015 but the directions at the link below do not necessarily always work as advertised.

Tried to get the ball rolling only with a VS 2015 build, running VS as admin.  It would not work.  Also, I had to build the support projects before doing the solution build.  The Client Dependency Core could not build for some reason when only Build Solution was done.  There was an error thrown that its DLL wasn't available.

Had to set up a DB with SQL Auth, set up a login for it, edit the connection string in the web.config after the build.

Then browsed with Chrome and to get install happening.  I'm sure there's a set up reason of some sort on my end where building with VS 2015 alone didn't work.

Just in case anyone else runs into these hurdles, this was my user experience.

Thanks,

Mike Durthaler
 
 Page 1 of 1
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Building DNN 8 with VS 2017 apparently causing source install issuesBuilding DNN 8 with VS 2017 apparently causing source install issues


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