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.0Debugging using IIS built into VS2008 (redirect problems)Debugging using IIS built into VS2008 (redirect problems)
Previous
 
Next
New Post
10/11/2009 12:45 AM
 

I'm trying to set DNN 5.01 up in VS2008 so I can develop against it.  With previous versions of DNN this was relatively simple with me just going in and adding a portal alias in the form:

localhost:1234/website

when DNN was installed in a folder named "website".  Now this isn't working.

I've read all the threads about port numbers not working well in 5.xx and I've uncommented "UsePortalNumber" and added the correct portal alias through SQL Server.  However I still get the redirect error.

I would like to run DNN from the web server within VS2008 so I can debug and set breakpoints.  I'm sure I'm not the first to encounter this problem.  How are other people doing DNN 5.xx development and debugging?

Thanks,

BK

 
New Post
10/12/2009 10:19 AM
 

I guess it would be helpful if anyone could confirm that they are indeed able to do module development agains 5.01 or greater.  Are you able to get redirection to work so that you can debug in Visual Studio 2008 and set breakpoints?

I just want to know that it's possible and working - I won't pester you with questions about your setup.

My next steps are:

Flush DNS and try again

Delete the Visual Studio project, rebuild and try again

Try to move the website around so the portal alias is locahost:1234 rather than localhost:1234/website and try again

Install a fresh copy of 5.01.02, migrate all of my custom modules and skins and try again.

thanks,

BK

 
New Post
10/12/2009 10:29 AM
 

Personally I recommend using IIS rather than the built in VS web server for working with DNN.  It simplifies a lot of things.


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
10/12/2009 10:36 AM
 

I'd like to do that too but I'm not sure it's possible.  My IIS6 is running on a server across the network.  I have it pointed at this website and that's how I"ve gotten as much of the work done on this site as I have.  But I don't know if it's possible to connect the debugging facility of VS2008 running on my workstation with the IIS running on my server.

If this is what you're doing can you point me to an article with info about setting it up?

Thanks

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Debugging using IIS built into VS2008 (redirect problems)Debugging using IIS built into VS2008 (redirect problems)


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