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 ...Root issue after InstallRoot issue after Install
Previous
 
Next
New Post
2/6/2010 7:22 PM
 
mush490

Joined: 4/14/2007
Posts: 2

Hi,  I've succesfully installed DotNetNuke and I am able to navigate to the home page.  I am using the Cassini web server. The problem is that none of the links work because the links point to http://localhost/ rather than http://localhost:3747/, the port that was assigned by Cassini.  If I enter the links manually in the browser, ie http://localhost:3747/Home.aspx, it works.  It seems that the root on my site is incorrect.  I updated the HostUrl column on the HostSettings table with no luck.  Does anyone know what I should be doing?  Thanks in advance for your help. 

Thanks!

Mike
 
New Post
2/7/2010 7:21 AM
 
Dylan (www.innosoftware.net)


Joined: 8/13/2006
Posts: 19

Hi Mike,

The Cassini web server isn't really intended to be browsed to "manually". Though you can often access a website by putting in localhost and the port Cassini assigned that isn't how you should go about doing it.

If you prefer Cassini, then run the DotNetNuke solution from the debug menu or hitting the 'play button' in the toolbar. Alternatively you can do what I prefer which is to host it in IIS on your development machine. On Windows XP is IIS is installed you launch it from Start > Run > 'inetmgr'. Here you can change the default website to the path where the DNN installation is. Typically the binding for 'localhost' is already setup in the default website.

When this is done, you won't need the Cassini port. Just go to the IIS hosted site (i.e. localhost) in a web browser. Then, to connect your .NET development environment to it just go to 'Debug > Attach to Process'. Here you can select the worker process running the website locally. I use Windows Vista Professional so it is 'w3wp.exe' in my processes list.

So again, you can either connect to the worker process after opening your site in a browser after hosting it in IIS, OR

You can launch the solution from Visual Studio .NET so it launches a browser to the correct port used by Cassini.

NOTE: Using IIS in XP isn't as good as Vista. The IIS in XP only allows you to host a single website at a time. Vista Professional allows many.

Good luck, Dylan

Dylan Lopez - Solution Developer, INNO Software Inc. E: http://www.innosoftware.net/contact.aspx P: 1-888-INNO-001 / 604-628-4467 W: http://www.innosoftware.net
 
New Post
2/7/2010 8:48 AM
 
mush490

Joined: 4/14/2007
Posts: 2

Hey Dylan, thanks for your response.  I'm only using Cassini out of necessity.  Unfortunately, I am running XP Home, so I do not have IIS available to me.  Through some research I found that you can install IIS on XP Home but I do not have a Windows 2000 disk, as required by the instructions that I found. 

When I open the DotNetNuke solution in VS2008, I get an error stating 'Unable to open website http://localhost/DotNetNuke_Community', Im guessing this is because of my lack of IIS.  I then try to run the solution and get an error stating that 'a project with output type class cannot be started directly'.

Is there something I need to do to point the DotNetNuke_community website to the correct port?  Is there anything else that I am missing?

Thanks,

Mike
 
New Post
2/8/2010 10:40 AM
 
Dylan (www.innosoftware.net)


Joined: 8/13/2006
Posts: 19

Mike,

The DotNetNuke solution is a collection of projects that make up the whole. Specifically there is the main one you are trying to run (DotNetNuke.Library) as well as supportive projects (HttpModules, Modules, Providers).

The project that fails to open is the actual website, this is what you'd run if it was working on your machine. By default it is configured to go to IIS (which, you don't have) and it looks for 'http://localhost/DotNetNuke_Community' which is the binding you'd need configured in IIS. There is good news though...

Factoid: To know the application type, right-click on 'DotNetNuke.Library' and choose properties. You'll see that the 'Application type' says 'Class Library' and under 'Compile' you can see that it outputs to the bin\ folder. This would only matter to you if you were modifying the core DotNetNuke project. If you want to do custom module development you actually never need to update the core DotNetNuke projects.

What you need to do, is tell Visual Studio that you haven't got IIS and want it to use Cassini. Also, to avoid the error about trying to directly starting a class you'll need to change the default startup project. Here are some tips:

1. Right-click on the 'http://localhost/DotNetNuke_Community' website project and go to 'properties'. You'll notice under 'Start Options' Visual Studio wants to know what web server to run this under. If it is set to 'Use default Web server' and 'ASP.NET' for debuggers then you're off to a good start.

2. For sake of getting the connection between the 'DotNetNuke.Library' project and this website, I highly recommend browsing the 'References' section to see how all the classes are used in this site.

3. Get out of the properties menu and right-click on the 'http://localhost/DotNetNuke_Community' website. Choose 'Set as StartUp Project'. This will make your hitting the 'play' button or 'Debug > Start Debugging' launch THIS project and not the class library project. To confirm you did this correctly try hitting F5 and you should be prompted to 'modify the web.config to have debug=true'. Say yes to this and you're good to go. (This is how Cassini is forced, you can't set the port they are randomly assigned and change very frequently.)

Word of advice though, get an OS with IIS. Ideally Vista or the Windows 7 professional editions. Having unlimited websites you can configure allows you to have many different instances of DotNetNuke going and be able to quickly attach to processes for debugging. I find it faster (no stop/start of the project), more robust (see: many instances) and let's not forget the "look how cool I am, I can attach to the IIS worker process" factor. ;)

Cheers, Dylan

Dylan Lopez - Solution Developer, INNO Software Inc. E: http://www.innosoftware.net/contact.aspx P: 1-888-INNO-001 / 604-628-4467 W: http://www.innosoftware.net
 
 Page 1 of 1
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Root issue after InstallRoot issue after Install


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