Products

Solutions

Resources

Partners

Community

Blog

About

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...Getting StartedGetting Started2 bugs in Source package2 bugs in Source package
Previous
 
Next
New Post
10/15/2012 8:04 AM
 

I would like to start to develop under DNN. I just downloaded

Source Code Package »

Contains everything including full application source code. 


but I have 2 problems:

1) When I configure IIS site pointed to /DotNetNuke_Community/ web site, I get this error, even with configure connectionString

Server Error in '/' Application.

Object reference not set to an instance of an object.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error: 

Line 561: //first call GetProviderPath - this insures that the Database is Initialised correctly Line 562: //and also generates the appropriate error message if it cannot be initialised correctly Line 563: string strMessage = DataProvider.Instance().GetProviderPath(); Line 564: //get current database version from DB Line 565: if (!strMessage.StartsWith("ERROR:"))

Source File: c:\ttt\!!!!!!!\NewDNN\DotNetNuke_Community_06.02.03_Source\Community\Library\Common\Globals.cs    Line: 563 

Stack Trace: 

[NullReferenceException: Object reference not set to an instance of an object.] DotNetNuke.Common.Globals.get_Status() in c:\ttt\!!!!!!!\NewDNN\DotNetNuke_Community_06.02.03_Source\Community\Library\Common\Globals.cs:563 DotNetNuke.Common.Initialize.CheckVersion(HttpApplication app) in c:\ttt\!!!!!!!\NewDNN\DotNetNuke_Community_06.02.03_Source\Community\Library\Common\Initialize.cs:116 DotNetNuke.Common.Initialize.InitializeApp(HttpApplication app) in c:\ttt\!!!!!!!\NewDNN\DotNetNuke_Community_06.02.03_Source\Community\Library\Common\Initialize.cs:181 DotNetNuke.Common.Initialize.Init(HttpApplication app) in c:\ttt\!!!!!!!\NewDNN\DotNetNuke_Community_06.02.03_Source\Community\Library\Common\Initialize.cs:275 DotNetNuke.Web.Common.Internal.DotNetNukeHttpApplication.Application_BeginRequest(Object sender, EventArgs e) in c:\ttt\!!!!!!!\NewDNN\DotNetNuke_Community_06.02.03_Source\Community\DotNetNuke.Web\Common\DotNetNukeHttpApplication.cs:161 System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +79 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +164 

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.17929


2) I can't publish web site, error:

Error 108 The type or namespace name 'DDRMenu' does not exist in the namespace 'DotNetNuke.Web' (are you missing an assembly reference?) C:\DotNetNuke_Community_06.02.04_Source\website\admin\ControlPanel\RibbonBar.ascx.cs 149


Error 109 The name 'adminMenus' does not exist in the current context C:\DotNetNuke_Community_06.02.04_Source\website\admin\ControlPanel\RibbonBar.ascx.cs 302

 
New Post
10/15/2012 8:58 AM
 

Note that you do not need to use the DotNetNuke source package when developing modules nor would I advise trying to build and install the source package unless you are quite experienced with setting up the install package.

Most likely your errors are due to not having . . .

1. Renamed website\release.config or website\development.config to web.config.
2. Built all projects (except the website project) in Visual Studio 2010 or 2012.
3. Properly set up your environment in IIS and SQL Server and granted full file system permissions on the webite folder to the ASP.Net worker process account.

If you still want to install the source package, please see the following Wiki page on this subject:

http://www.dotnetnuke.com/Resources/W...

Also, please note that you cannot use Visual Studio's publish website tool with DotNetNuke nor should you pre-compile the website project as it will be compiled "on-the-fly" when the site is first visited or following an ASP.Net worker process timeout due to inactivity.


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
10/15/2012 9:59 AM
 
Using the source package Needs first building the Visual Studio Projects and then compile all projects. Compiling the projects is need to build all files for the Website.
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Getting StartedGetting Started2 bugs in Source package2 bugs in Source package


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