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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Problem Using DNN 4.9.1 Source Code Version - Second TryProblem Using DNN 4.9.1 Source Code Version - Second Try
Previous
 
Next
New Post
2/11/2009 12:24 PM
 

I am using Visual Studio 2005, together with MS SQL 2005 AND the Source version of DNN 4.9.1 on a Windows Server 2003, Service Pack 2.

I have the following problem trying to use the source code version of DNN 4.9.1:

  1. I installed DNN with DotNetNuke_04.09.01_StarterKit.vsi.
  2. I created a DNN Web project, set the permissions, edited connection strings to point to MS SQL 2005 database I had created (adding Network Service user with permissions).  Just a no-bells&whistles install, I did not add any skins or modules to the project.
  3. I then ran the project added a "localhost/DotNetNuke_Maintenance" port alias.
  4. I then made a backup of the database just configured by the above steps.

Next I wanted to set up a Source Code project, so I did the following:

  1. I then did a restore of the backup just made to replicate the database (adding in Network Service permissions).
  2. I then extracted the source version into a directory, set up the permissions, copyied release.config to web.config, edited the database connection string.
  3. I then created a Web (using a Virtual Directory, the solution will not load in VS), calling it "DotNetNuke_Maintenance" and pointing it to the "Webfiles" directory in the source. I set the permissions for Network Service and made sure .NET version was correct.

After doing all this, I can load the solution in VS and compile it.  But, when I try to run (Ctrl+F5) the project, I always get the following:

Server Error in '/' Application.
--------------------------------------------------------------------------------

The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable.  Please review the following URL and make sure that it is spelled correctly.

Requested URL: /DotNetNuke_Maintenance/Default.aspx


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433


I have been (periodically) banging my head against this issue of trying to get a source code project working for more than 2 weeks (my last question here was not responded to). 

Is it perhaps something to do with pointing the Website to the Webfiles directory that I'm not catching?  I've tried it various ways and put the source code directory right on the root of the drive.  It seems the permissions are set.

When I get the error message shown above, the browser shows it is going to "http://localhost/DotNetNuke_Maintenance/Default.aspx".

Does this problem ring a bell for anyone?  This must have come up before, but I can find it dealt with.  I would like to be able to run DNN in debug mode with the full source code. Is there a better way?  I would sure appreciate some help.

 

 
New Post
2/11/2009 8:45 PM
 

I'm not sure why you're using two versions. The easiest way to get this working is to download the source version, rename release.config to web.config, recompile the solution, start the IIS start page and press F5 (alternatively edit the sln file and change the path

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
2/11/2009 9:07 PM
 

Cathal -you don't even need to recompile the solution. I use this (the source version) with oracle dp and I never recompile the source. Simply rename release.config to web.config (like you pointed out) and make sure I point to the right db...
The only time I open it up in VS is if I have to debug something not working in which case I modify the sln file to point to my virtual directory...

Sanjay


AcuitiDP - Oracle Data Provider for DotNetNuke
 
New Post
2/11/2009 9:11 PM
 

langkd - here's what I'd suggest...
Unzip source copy to new folder. Modify IIS to point to new unzip files (website subfolder is correct). Make changes in web.config to point to correct db and also make sure you copy your machine keys over from the original web.config. Fire up the site in IE and it should come up. If you want to debug, modify the sln file to point to Dotnetnuke_maintenance (assuming your virtual directory is named as such) and attach the W3 process instead of hitting F5.

Also what version of IIS are you using? In IIS 7, I believe you have to Add Application and not add virtual directory...

 


AcuitiDP - Oracle Data Provider for DotNetNuke
 
New Post
2/12/2009 8:00 AM
 

Sanjay, I agree that often you don't need to recompile the source version but it's a good practice, just in case there are dependencies that you may have missed as they'll be identified immeadiately e.g. dnn 5 requires ms ajax, so it would pick up if that dependency was missing.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Problem Using DNN 4.9.1 Source Code Version - Second TryProblem Using DNN 4.9.1 Source Code Version - Second Try


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