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...DNN Platform (o...DNN Platform (o...Run existing installation from Visual StudioRun existing installation from Visual Studio
Previous
 
Next
New Post
2/10/2009 10:48 AM
 

I was wondering if, just to develop, I could run an existing installation (that is running now with IIS) entirely from VS or Web Developer Express, without IIS. As with the instructions described here.

When I do this (open the root of the site with the "Open Website" option) and run the site, I see it first running, for example at "http://localhost:65369/DotNetNuke", using the development server as expected, but then there is a redirection to "http://localhost/dnn" (the site in IIS). So I still need to have the site configured in IIS.

This also happen with a fresh install, if I first configured and installed it with IIS (doesn't happen if I run it from VS from the first moment, like in Michael's guide) and then want to run it just with VS.

Maybe there is a setting or something else telling the site to run using the IIS URL?

This isn't a big trouble, but I would like to be able to develop modules for this site and run it without IIS, using just the development server.

 

Thanks so much in advance

 
New Post
2/10/2009 3:52 PM
 

yes, you can do that. You have a few choices - you can add the localhost:65369 entry as a portal alias and then you'll be able to use it. Alternatively, you can use the project properties to set the localhost IIS entry as the start point, and disable dynamic ports (which is generating the 65369 entry)

However, the easiest way to do this is to download the starterkit and install it - you'll then be able to create a new website using the dotnetnuke template, and run it within vs.net without IIS.

Cathal


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

Thanks for the answer.


I think my problem also was caused because the root directory name of the site (DotNetNuke in my example) was different to the site name (dnn). I changed the directory name to match the name of the site and opened the directory from VS with the option "Open Website".
 

Now I have the same portal alias to run the site from VS or IIS: localhost/dnn
And, from VS, the site can run using (regardless the port) an url like: http://localhost:53029/dnn/

 
Previous
 
Next
HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...Run existing installation from Visual StudioRun existing installation from Visual Studio


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