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...Debugging with multiple host headersDebugging with multiple host headers
Previous
 
Next
New Post
3/12/2009 5:30 AM
 

Hi

Until now we developed modules on a server in a single Visual Studio .NET project (without source control etc.). Now we decided to use a source control and to develop on the local machine. I thought "no problem" and set up the necessary environment. What I didn't know (I'm a new employee of this company and im also new to DNN ;)):They use several host headers like dnn1.dev.company.com and dnn2.dev.company.com for different portals. So I ran in a problem when I tryed to debug the dnn web application locally with the integrated web server in Visual Studio. I think the problem seems to be the redirection to "dnn1.dev.company.com" at the beginning because the application starts with the url "localhost/website/Default.aspx". The browser can't find the Default.aspx (because of the virtual directory "website"?!). The other thing is even when I use a mapping in my hosts file the uri in the background is still localhost. It probably would work with IIS, but there's the next problem: IIS on a win xp computer supports just one website. Also a problem - a non dnn one: how can I switch the starting url in Visual Studio easily?

Is there a proper way to debug several portals with different host headers in Visual Studio 2008? I read about UltiDev Cassini WebServer that supports multiple host headers on a client computer. But I'm not sure if it supports all the third party software we use to extend DNN. An other tool I read about is IISAdmin that switches the active website in IIS.

I hope anyone understands my problem ;)

 
New Post
3/13/2009 4:50 PM
 

Let me ask you this...  Why do you need to switch between so may portals so often?  If you are just developing modules then you could consider creating a "dev" portal.  Use it for all of your primary debugging and testing needs.  Once your module is complete push it to these other portals as needed (for final testing and release to QA).

If you still find the need to do multiple portals, maybe consider switching your OS to a server sku with a full blown web server...?  Doesnt Vista's version of IIS7 support multiple sites?  (I always use Server2003 or 2008 as my primary dev OS).

 
Previous
 
Next
HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...Debugging with multiple host headersDebugging with multiple host headers


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