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 ...Setting up development environmentSetting up development environment
Previous
 
Next
New Post
2/2/2011 1:35 AM
 
Marc (ម៉ាក) Vanhemelryck (វ៉ាន់ហេមិលរីក)


Joined: 9/22/2006
Posts: 262
Sebastian Leupold wrote:
Regarding host options: I am not a fan of duplicating admin menu items in host menu. Like we did in the core with Languages module (there are still some other modules to follow) a single administration point will be easier to handle, of course, host options should be clearly marked either on the same control or on a separate one, accessible by a link visible for superusers only.

 I didn't reply, but I got your point.

____________________________________
The one-eyed in the land of the blind.
 
New Post
2/2/2011 2:51 AM
 
Marc (ម៉ាក) Vanhemelryck (វ៉ាន់ហេមិលរីក)


Joined: 9/22/2006
Posts: 262
I have now gone through all the versions since 5.04.04

All versions except the last direct their build outpot of CountryListBox to Website\bin. I will look into the countrylistbox project files to find the propper way to redirect that output. I did the setup of the 5.06.01 sources a second time, to make sure it came that way in the source files and was not the result of an unwitting modification of my part.

In the versions 5.06.00/01, Syndication, Taxonomy and Messaging lost references and DotNetNuke.Web lost its reference to the library. Does this belong in Gemini?

VS2008 is not very popular anymore nowadays, I see, as no-one spotted this.
____________________________________
The one-eyed in the land of the blind.
 
New Post
2/2/2011 6:05 AM
 
Marc (ម៉ាក) Vanhemelryck (វ៉ាន់ហេមិលរីក)


Joined: 9/22/2006
Posts: 262
So, I can make all versions compile, be it with issues. I can complete the installation of DNN 5.06.01 until I have a running portal. Let's see how that works with the other versions. The first version to be tested was 5.04.04.

I first had changed the output for the build of the CountryListBox.dll to the correct folder, then I built an instance of the dll, then I referred the library to the CountryListBox and Syndication and so on, until the solution compiled without errors. I checked Website\bin. While all other dlls were recent and had debug information, CountryListBox.dll dated from June 2010. So, one step had been missing.

Building the site:
Installing Database - Version 05.00.00...Success
Upgrading Database to Version 05.00.01...FAILURE  -

This did not seem very much related to the countrylistbox. To be sure, I went through the install process again, this time building the dll directly to Website\bin as the solution suggested. The same error occurred at the time of building the site. I will see if I can discover what SQL instruction ran into error.
____________________________________
The one-eyed in the land of the blind.
 
New Post
2/2/2011 7:29 AM
 
Marc (ម៉ាក) Vanhemelryck (វ៉ាន់ហេមិលរីក)


Joined: 9/22/2006
Posts: 262
Okay, I have to review my priorities. I thought it would have been a good idea to be able to debug against any version of DNN. While I still believe so, I wonder wether it is necessary to be able to debug with the source code of any DNN version. If it would have been possible to create an instance of DNN from the source code in 10 to 15 minutes, I would have seen that as an advantage. But if every version includes gotchas like here, I start doubting the wisdom thereof. I can do my debugging just as well against a normal DNN installation.

DNN 050600 includes syndication as a C# project, which totally refuses to co-operate:
------ Build started: Project: DotNetNuke.Syndication.VS2008, Configuration: Debug Any CPU ------
DotNetNuke.Syndication.VS2008 -> D:\Development\dnn050600\Library\Components\Syndication\bin\DotNetNuke.Services.Syndication.dll
D:\Development\dnn050600\Library\Components\Syndication\DotNetNuke.Syndication.VS2008.csproj(113,5): error MSB3021: Unable to copy
 file "bin\DotNetNuke.Services.Syndication.xml" to "..\..\..\Website\bin\DotNetNuke.Services.Syndication.xml". Could not find
file 'bin\DotNetNuke.Services.Syndication.xml'.
Done building project "DotNetNuke.Syndication.VS2008.csproj" -- FAILED.
========== Build: 0 succeeded or up-to-date, 1 failed, 0 skipped ==========

In the compile property page of the cproj, it is told to create the xml file in the bin folder.

These older versions are not going to be modified anyway. DNN 5.06.01 does compile and does start. That error is gone. I can live with the issues that are left, but the DNN team should make it a point of honor to make that the open source version at least compiles as is. I'm going to skip DNN 5.05, there is little I might still learn from the experience.

So, I will keep my source setup always running the latest DNN version. Tests against other DNN versions will have to take place without the sources available. But please, keep future versions installable!  What if this happens again?
____________________________________
The one-eyed in the land of the blind.
 
 Page 3 of 3
Previous123 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Setting up development environmentSetting up development environment


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