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 ...DNN 5.6.2 Source Installation IssuesDNN 5.6.2 Source Installation Issues
Previous
 
Next
New Post
6/29/2011 5:37 PM
 
G Mitchell


Joined: 3/5/2004
Posts: 180

Hi Folks,

I wasn’t sure where to post this since there are multiple issues. If it should be posted elsewhere let me know.

This may be a bit long but the details may be important.

I am having a problem with a custom module built for DNN 4.x. I was running OK on 4.9.5. This module uses a special database in addition to the standard one and I could not seem to upgrade from 4.9.5 to 5.4.4 following the recommended path to finally get to 5.6.2.

Using the workaround here - Possible problem in the Dotnetnuke core lib on ver 5.x It seemed to work except for this:

00:00:32.078 -   Executing Application Upgrades: 05.04.03 Error!

I am not sure if that is a critical issue but the site works except for one thing. My module which uses the Microsoft GridView component to view and edit the data in the special database does not. At that point I decided to create a 5.6.2 site with the source version and use that to help debug my module. I did that with 4.9.5 a good while back. Here is where I am now:

I created a 5.6.2 site using the community source version following - How to Install the Source Package of DotNetNuke. I got a whole bunch of errors when I did a build on the solution, over 100. Just for drill I ran the build again and got 22 errors! I then did a website build and got one error. This one - Error BC30456: “Framework” is not a Member of “DotNetNuke.UI.Skins.Controls.DotNetNuke” I used the fix in that post and got a clean build. Then again just for drill I did a build on the solution and then a rebuild on the solution. There were no errors!

This was all a little disconcerting since I don’t recall having this much trouble with older versions of DNN source builds. I have always set up a site based on the source locally for testing purposes.

Before forging ahead I thought I would just get some input from some of you folks who have more experience with DNN especially the source version. Are there special steps to get a clean build the first time? BTW, I am using VS 2008 on Win XP SP3 and IIS 5.1.

Sorry for the length.

 

This whole experience was a little bizarre and I get worried if I don’t understand what is going on even if things appear to work. Any advice or comments would be much appreciated.

Thanks,
George
 
New Post
6/29/2011 8:58 PM
 
William Severance


www.wesnetdesigns.com
Joined: 2/18/2005
Posts: 3253
I have built source installations of most of the DNN versions since 3.3.1 or so and have been impressed as to how well builds of the later 5.x versions have gone without the many build errors raised in earlier versions. When setting of a source install of 5.6.2 I recall receiving only one error - that one of the project's .xml files (can't recall which one now) could not be copied to the Website/bin folder. That error can be ignored and will not re-occur on a second build.

If you receive as many errors as you did the cause was likely one of the following:

1. You did not first open in notepad and modify the solution file (DotNetNuke_Community.sln) before opening it in VS 2008 to change the yellow highlighted section of the following line to point to the correct URL for your particular website installation:

Project("{E24C65DC-7377-472B-9ABA-BC803B73C61A}") = "DotNetNuke_Community", "http://localhost/DotNetNuke_Community", "{A27249DD-8437-43C0-93D6-10600045B8F6}"

2. You did not rename Website/release.config or Website/debug.config to web.config prior to opening the solution in VS 2008.

If either of these steps are missed, some of  the projects in the solution will not be able to find the various namespace imports in the web.config file and will indeed have many (100's) of build errors.

3. Another cause of build errors is including the website (WSP) project itself in the build configuration. As of DNN 5.6.2 it is still not possible to pre-compile the website itself without error so be sure that the Build checkbox for the website project is NOT checked in the solution's build  configuration. The website project will be compiled "just in time" when first visited.



Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
6/30/2011 1:23 PM
 
G Mitchell


Joined: 3/5/2004
Posts: 180
Thanks for the quick reply William. I thought I did everything you indicated. However, I went back and redid everything. When I open the project in VS2008 I get many errors immediately. That would indicate something wrong with the .sln file, correct? Could you look at that article I am following under the section Modifying the Visual Studio Solution File. The link to the article in in my initial post. Is there anything there I should not do?

Thanks,
George
 
New Post
6/30/2011 9:53 PM
 
William Severance


www.wesnetdesigns.com
Joined: 2/18/2005
Posts: 3253
I'm the author of the Wiki article to which you are referring so am very familiar with it. It sounds like you are following those steps so I'm not sure what if any steps you are missing.

What are the types errors that are shown when opening the .sln file in VS 2008? - Missing references? Missing namespaces? Obsolete (deprecated) methods?

On the possibility that your download of the source package was corrupted I'd suggest doing a new download from http://dotnetnuke.codeplex./releases. Before extracting the .zip package into your installation folder be sure to right click on the downloaded package icon or filename, select "Properties" from the context menu, and if there is an "Unblock" button click on it.

After extracting the .zip package, be sure to rename release.config or development.config to web.config.

Am I correct that you have properly added a new application in IIS, have assigned it an alias and pointed that alias to the Website folder (not the root folder) of the extracted package? Are you using an ASP.Net 3.5 or ASP.Net 4.0 application pool? Have you granted full filesystem permissions on the Website folder (and all child folders) to the correct ASP.Net worker process account, i.e. the AppPool Identity user?

Make sure that you  (before opening the .sln file in VS 2008) first open the .sln file in Notepad or other text editor and make the changes to the website project url as indicated in the yellow highlighted text in my first reply and as indicated in the Wiki.

After opening the solution file in VS 2008, open the Build --> Build Configuration Manager, select your desired Debug or Release configuration and make sure that all solution projects (EXCEPT the DotNetNuke_Community website project) are checked. Then Build the solution.
Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
7/1/2011 11:36 AM
 
G Mitchell


Joined: 3/5/2004
Posts: 180

Thanks Bill. I pretty much came to the same conclusion, i.e. I would have to clean everything off connected to the 5.6.2 source and completely start over. Your instructions in that Wiki article are very complete. I'll go through them again along with what you posted here methodically and take my time so I don't miss anything.

I am running on Win XP SP3 with IIS 5.1. I have .NET Framework 3.5 SP1 installed. Are there any possible environmental factors I might be messing up on? BTW, I do have a regular install version of 5.6.2 running on this hardware with no problems.

Just for drill here are some sample errors:

Error 4 'CountryLookup' is not a member of 'WebControls'. C:\Visual Studio Projects 2\DNNSRC562\Library\Entities\Modules\UserModuleBase.vb 406 51 DotNetNuke.Library.VS2008

Error 5 Type 'DotNetNuke.UI.WebControls.CountryLookup' is not defined. C:\Visual Studio Projects 2\DNNSRC562\Library\Entities\Modules\UserModuleBase.vb 417 35 DotNetNuke.Library.VS2008

Error 16 Name 'Channel' is not declared. C:\Visual Studio Projects 2\DNNSRC562\Library\Services\Syndication\RssHandler.vb 26 17 DotNetNuke.Library.VS2008

Error 257 'Model' is not a member of 'System.Web.UI.WebControls.View'. C:\Visual Studio Projects 2\DNNSRC562\Modules\Messaging\Presenters\EditMessagePresenter.vb 183 56 DotNetNuke.Modules.Messaging.VS2008

 
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN 5.6.2 Source Installation IssuesDNN 5.6.2 Source Installation 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